Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp625459rwd; Thu, 18 May 2023 01:23:18 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6Dwju/81LZ4bQGBGokAP7NPnLDYrebIXgaJqM6NRo0gXPkACptsyxocMrNlffIvPCPWJhv X-Received: by 2002:a17:902:b210:b0:1a9:bac2:21a2 with SMTP id t16-20020a170902b21000b001a9bac221a2mr1391445plr.21.1684398198142; Thu, 18 May 2023 01:23:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1684398198; cv=none; d=google.com; s=arc-20160816; b=Hz2vY93r/eOW79URlhgu+9UxP7hW+WYSNs20RxFW5xrJXWOh3bPpJ0W+3gSdclBQxz ocLF1tbvGGyiay8Rll1m6vkj2U0q4gTk5xd1y7a6chyhg35GCmeHzahflKJpbJyh8xir x8qQ2HZY3x6EtyBVYQM/grYvjb2hG6OIoVQQQSlPUOryTbwb6OgDZqq5BABXAbkmjgFF O26PUgY1rgCtFsSBjAwW9agbHjCyydNmCAe/osp6pBo+e/5H1XgouNIlxd+EHeZgM53N 0j/D6fsfDkuFBMS+zibJoKLDb5QozGbXSFs1E0ATzJy96PM+zcVy04/aFIJNtpu7fMjj Mimg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :dkim-signature; bh=35wFhivmcYCWnVrRWAiYgC66ZHYrppThfjDiaL7jSDs=; b=xji6kZ6y2kmh4sRMdN8RVaKfk3SbnMktJuqxdhZbpKyCQ7nDc7nFxVfCPgMqm8mZTa N8b5axChgB3gMSLeyGzD1fLVeyuQOo4LPJ6GTeTFZw0rOmMei6nroYPrTPYWSS/O7bP0 0GCWJO3f5JdjflOmMa57pn7aQfhjQF4syh8VLiBTg6piIF7Cq0icD8Sh3MUpdGfXw+Av GENdrprHFW3wgcjE4etk0hnS6Y++nUKHtk6Vsfl+CbnOn+cYv5JIZUSkYp8f11Raz2xw 80zT4jss00Isiv9OUU2ejc003nlfo1K0TLOKU4kB4JWd6bQ+bEXgwq37ou0IE0opH3Is 6Osg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=gNaF4FEF; dkim=neutral (no key) header.i=@suse.de header.b=mMuwCITD; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id u16-20020a17090341d000b001add3e9cc4bsi745304ple.535.2023.05.18.01.23.06; Thu, 18 May 2023 01:23:18 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=gNaF4FEF; dkim=neutral (no key) header.i=@suse.de header.b=mMuwCITD; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229987AbjERHwR (ORCPT + 99 others); Thu, 18 May 2023 03:52:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40936 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229669AbjERHwP (ORCPT ); Thu, 18 May 2023 03:52:15 -0400 Received: from smtp-out1.suse.de (smtp-out1.suse.de [IPv6:2001:67c:2178:6::1c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4D9512699; Thu, 18 May 2023 00:52:14 -0700 (PDT) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 199CF22618; Thu, 18 May 2023 07:52:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1684396332; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=35wFhivmcYCWnVrRWAiYgC66ZHYrppThfjDiaL7jSDs=; b=gNaF4FEF4sCEAoxMytxwRr24GdjT8ysJtK4mZVMdB6U7mOAaNy9+e/8ROl4bTWmVE5p2kl ooY4Tybp8d+N0Zie0mPzgBkdlsvfONKgCMPjMyzpz1gUj3RknDCfNKrjI3JTVeS6zUHnpB 4yVehVoifvGbZDr8er2poJBS5RZ3/HI= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1684396332; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=35wFhivmcYCWnVrRWAiYgC66ZHYrppThfjDiaL7jSDs=; b=mMuwCITDzTnnCtb0M9rvVEUBnsoij5qy+Bez40xgUbr1ldcfQWzVPwim0FVUDQ2efW9cQO V0qP84RymdNjyrBw== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 08CAE1390B; Thu, 18 May 2023 07:52:12 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id iU/FASzZZWRpKQAAMHmgww (envelope-from ); Thu, 18 May 2023 07:52:12 +0000 Date: Thu, 18 May 2023 09:52:11 +0200 From: Daniel Wagner To: Chaitanya Kulkarni Cc: "linux-nvme@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "linux-block@vger.kernel.org" , Shin'ichiro Kawasaki , Hannes Reinecke Subject: Re: [PATCH blktests v4 05/11] nvme{032,040}: Use runtime fio background jobs Message-ID: References: <20230511140953.17609-1-dwagner@suse.de> <20230511140953.17609-6-dwagner@suse.de> <50c50cda-23f5-b55d-a902-ce34de8498e1@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50c50cda-23f5-b55d-a902-ce34de8498e1@nvidia.com> X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 17, 2023 at 04:40:52AM +0000, Chaitanya Kulkarni wrote: > On 5/11/23 07:09, Daniel Wagner wrote: > > The fio jobs are supposed to run long in background during the test. > > Instead relying on a job size use explicit runtime for this. > > > > Signed-off-by: Daniel Wagner > > Is there any issue with the exiting approach for this change ? The expectation of the test here is that there is a background job running. Depending on the job size is an indirect way to express run at least for x seconds. This gives a variable runtime as it depends the how fast fio jobs gets executed. Explicitly telling the runtime is my opinion more robust and documents the indention better.