Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp7633723rwr; Wed, 10 May 2023 10:30:36 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ5yrzBvjX/BDszf5YutI46XiV9OSsIb8whX8dEVqI3P0B44H/MwCPdmuZISIOxCvhOehmls X-Received: by 2002:a17:903:338e:b0:1a8:ce:afd1 with SMTP id kb14-20020a170903338e00b001a800ceafd1mr16984115plb.20.1683739835862; Wed, 10 May 2023 10:30:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683739835; cv=none; d=google.com; s=arc-20160816; b=g7sq3skKc8K30RqtoW+3m9muBLzbZiAtpmG0peeeRzGA1Qpl1vsDHfvHBAYtCIDNEY htEq8R1kkncBLU+dlGpElQv9SnCTp2I4yXQIvw3WcTs8ihkBZK7mb7WPde2ssMb5Nuoa pL0whRJzj7mzUPIB2TvO00MDrDFj5uO9FyDaAJPthX7U/DUDtoYy5BKjczzjD8iTgEu4 x4TEvHineHcUqw0bBB0QtWPh32iA1Lve/sh9BHnOL2qddLzGNSR16729YtxZlANQWbTd 0RTAfMGyVjrrh7/8t2DUVyCwRdzVdaiZCserofbiXayErd1yWsAq7OPjF4lAFKSrW1NQ PM+Q== 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=+2RPcnuD/B5/jpEGRvPjSZU9zdchad+gheYdPhvKsik=; b=EJEvQtz4BbaAJdFTaaTWd+Dn0t2kY7zTklyuzncIlmvB08pOBb7RqEBrxTRP8khRa/ RKfTAgClciUoOAg2Jj5w/k/KunvC4zzci7UybsI7MWRdyY/ZieEvWOm8AIRBkcRpqubD Qez2juOvaF0d+k2h0fXBfi8iLuxpC+sFWTBePk8LWmusAxvXnSUF8C/dhyI7NkK80IIL Rruv9N+1mORJEsLzwfkR0sjTL0ohJxJB0RyP0DV2lEm50K5P7SCYeHrDzyKgcx/mTr+F V8OFaN7M8EurSbM3FzR8rOmKSlvgo8WemNeseBc2fKGX23Zo60Rp4+VqG8ZywkPL8/hE tTuQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=CDhVusS9; 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 a13-20020a170902eccd00b0019c33978781si4730695plh.283.2023.05.10.10.30.20; Wed, 10 May 2023 10:30:35 -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=CDhVusS9; 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 S236614AbjEJRPA (ORCPT + 99 others); Wed, 10 May 2023 13:15:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58432 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236657AbjEJROt (ORCPT ); Wed, 10 May 2023 13:14:49 -0400 Received: from smtp-out2.suse.de (smtp-out2.suse.de [IPv6:2001:67c:2178:6::1d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E397F4203; Wed, 10 May 2023 10:14:27 -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 D5A581F747; Wed, 10 May 2023 17:14:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1683738864; 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=+2RPcnuD/B5/jpEGRvPjSZU9zdchad+gheYdPhvKsik=; b=CDhVusS9912eGykAiQg6jDXMItwGdq4OE7PYs9GVcisKsjLU9Ik0z5HcqXvw98UMJmZNUh RhZ+NcOiLFCSKWbpVFHP1Zwad+oTKc0Oh4kGJY1gEjR5EYnBLS7bsllaSZQ0sF5Z4BKS8v dLXHCyJthyPPYg7i+ssI+LGL80Z109E= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1683738864; 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=+2RPcnuD/B5/jpEGRvPjSZU9zdchad+gheYdPhvKsik=; b=+MV2TCiVhwrQVmQhz0kE4dKRD3/8Sq2ueROZPM78U8lF9yXdmTnCmGdTfBimjYWSFH/H82 ckOAlFD5+0bsLJDg== 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 37BE413519; Wed, 10 May 2023 17:14:23 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id eGEpOe/QW2SZCAAAMHmgww (envelope-from ); Wed, 10 May 2023 17:14:23 +0000 Date: Wed, 10 May 2023 19:14:21 +0200 From: Daniel Wagner To: Shinichiro Kawasaki Cc: "linux-nvme@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "linux-block@vger.kernel.org" , Chaitanya Kulkarni , Shin'ichiro Kawasaki , Hannes Reinecke Subject: Re: [PATCH blktests v3 10/12] nvme/rc: Calculate IO size for random fio jobs Message-ID: References: <20230503080258.14525-1-dwagner@suse.de> <20230503080258.14525-11-dwagner@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Sun, May 07, 2023 at 11:31:10PM +0000, Shinichiro Kawasaki wrote: > - _xfs_run_fio_verify_io /dev/"${nvmedev}n1" "1m" || echo FAIL > > + rand_io_size="$(_nvme_calc_rand_io_size 4M)" > > + _run_fio_rand_io --filename="/dev/${nvmedev}n1" --size="${rand_io_size}" > > Here, _xfs_run_fio_verify_io is replaced with _run_fio_rand_io. May I confirm > that this replacement does not affect this test case? Same question for the hunk > below. This is on purpose. The test just wants only verify that IO is still working. Because _xfs_run_fio_verify_io has the minimum requirement of 350M for nvme_img_size. When I wrote the test I didn't know this and thus this change. I'll update the commit message to include this info.