Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp1853621rwr; Fri, 21 Apr 2023 00:02:33 -0700 (PDT) X-Google-Smtp-Source: AKy350a0kDcU0ogHo5ExEig7TGfsOMbOV7aHBMtxe1lDu24b7+9zX7usVjOttSmJaEnDpx+s+4D5 X-Received: by 2002:a17:90b:1e04:b0:249:86ef:f7e2 with SMTP id pg4-20020a17090b1e0400b0024986eff7e2mr4362682pjb.31.1682060552622; Fri, 21 Apr 2023 00:02:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1682060552; cv=none; d=google.com; s=arc-20160816; b=HhQFer3Bk1spUQEtzUqi1oQIx4VcN19h8fVea5OxJiQFV0djuCjNEXO13HMGSVwPJq +pfsFT85woBqXXWUWq54LMbWk8SzfpJm1cQvtx4T88uEFXfubC1NI8fwIDDDIszUns0X +s9aqqafz5sM3H7eHkyTDwFlpDQkXwNO86asDgJ2KzbWMTJPUIk+JfHvJ1k8+urUS9Hq 0Nu+6zm/sV3JgRKztTCI+Ll/zbexLycP/jQxLFUR75ciJEdoNcl6VeXr1nbyUcnyPKyO jBjXB1YNJfLw5AGkpiXdtWRWh7umWkJ2Vh5Z/erW7O/ARiDwYPAv7i5Tvsagf2gE5Xsw HAwA== 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=HxUKKIOGPl7o2Ksj+0VHAq6dun13rkhfrfvtHYNmQtc=; b=zxvPTh9cs4lOlNrq7xgL6xDPuT8OJPH3BlFkY2bLKbtt3wxN5KMXsahKMO3OjsJjR6 THfZLBSz+J6yvH+p1ao0fp3SNFbS/aCgmklKQ8rI4fIQXCj/xON+lrEYEU//1PKLuQev 2RsO/Owi47Kv6qqmuvmn7NYfyUC4ke8e1F3KnwBvK0ucBELudBe4FFFUL1n8nYCkrO8i Y89QBN6OpN94eTxfCl0FmCszWq26qpkKvKIgav+mBbR3FOlpvc80BqxWbROfwgC9Nbei UC2cmggyqeSvDNCdADAznnALbBM2GMGlcR8+6KrsaIv3G6l/pfNnd8lf7p11UR29zBL3 ijqg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=v6mz9MMi; dkim=neutral (no key) header.i=@suse.de; 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 qe2-20020a17090b4f8200b00246d179dc81si4269595pjb.126.2023.04.21.00.02.12; Fri, 21 Apr 2023 00:02:32 -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=v6mz9MMi; dkim=neutral (no key) header.i=@suse.de; 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 S230297AbjDUG5v (ORCPT + 99 others); Fri, 21 Apr 2023 02:57:51 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46140 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230291AbjDUG5s (ORCPT ); Fri, 21 Apr 2023 02:57:48 -0400 Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 72E507DAF; Thu, 20 Apr 2023 23:57:45 -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-out2.suse.de (Postfix) with ESMTPS id 1688C1FDDC; Fri, 21 Apr 2023 06:57:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1682060264; 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=HxUKKIOGPl7o2Ksj+0VHAq6dun13rkhfrfvtHYNmQtc=; b=v6mz9MMie9djBV+bbusRwLIygoiB9KDAuM6Vr21UKpDrD+UMRSU9YcU/dNv52ZH0SrYG8c l/9n/KW6Z2al/j4HSxnhWAJ12bE3JGnpT4riMxBha/J4axcz1S0AlBzsyduM5pyhuuWuJp C/S5pQaDH7nbVzL+A0bdZHEfu9xVX+Q= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1682060264; 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=HxUKKIOGPl7o2Ksj+0VHAq6dun13rkhfrfvtHYNmQtc=; b=MqlTArYI6WN3lWuaDC+wZK1XuorzAqvJEvg0cUbM/MXxH3KZBbZ1N7iFzRacJMg2thU/LM 6OleX8aXj2mjU8DA== 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 0792313456; Fri, 21 Apr 2023 06:57:44 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id 5v3lAegzQmQTfgAAMHmgww (envelope-from ); Fri, 21 Apr 2023 06:57:44 +0000 Date: Fri, 21 Apr 2023 08:57:43 +0200 From: Daniel Wagner To: Hannes Reinecke Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, Chaitanya Kulkarni , Shin'ichiro Kawasaki Subject: Re: [PATCH REPOST blktests v2 4/9] nvme: Use runtime fio background jobs Message-ID: <4ckg7ymu73lfs7zlsby3com6k24qgovkaqky5jmgeoubs7azhh@jtvovyjluekv> References: <20230421060505.10132-1-dwagner@suse.de> <20230421060505.10132-5-dwagner@suse.de> <72ecc5fc-0ff4-5592-3293-f4204633fc8e@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <72ecc5fc-0ff4-5592-3293-f4204633fc8e@suse.de> 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,URIBL_BLOCKED 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 Fri, Apr 21, 2023 at 08:29:22AM +0200, Hannes Reinecke wrote: > --- a/tests/nvme/040 > > +++ b/tests/nvme/040 > > @@ -38,7 +38,8 @@ test() { > > # start fio job > > echo "starting background fio" > > _run_fio_rand_io --filename="/dev/${nvmedev}n1" --size=1g \ > > - --group_reporting --ramp_time=5 &> /dev/null & > > + --group_reporting --ramp_time=5 \ > > + --time_based --runtime=1m &> /dev/null & > > sleep 5 > > # do reset/remove operation > > Wouldn't it be better to let _run_fio_rand_io pick the correct size? Yes, makes sense.