mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Daniel Wagner <dwagner@suse.de>, linux-nvme@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
	Chaitanya Kulkarni <kch@nvidia.com>,
	Shin'ichiro Kawasaki <shinichiro@fastmail.com>
Subject: Re: [PATCH REPOST blktests v2 9/9] nvme: Make the number iterations configurable
Date: Fri, 21 Apr 2023 08:38:59 +0200	[thread overview]
Message-ID: <c5a5cf4b-ba96-1e55-26ac-d2da9ab7117d@suse.de> (raw)
In-Reply-To: <20230421060505.10132-10-dwagner@suse.de>

On 4/21/23 08:05, Daniel Wagner wrote:
> Some tests hard code high values of iterations. This makes them run
> relatively long compared to the other tests. Introduce a new environment
> variable nvme_num_iter to allow tune the runtime.
> 
> Signed-off-by: Daniel Wagner <dwagner@suse.de>
> ---
>   tests/nvme/002 | 2 +-
>   tests/nvme/016 | 2 +-
>   tests/nvme/017 | 2 +-
>   tests/nvme/rc  | 1 +
>   4 files changed, 4 insertions(+), 3 deletions(-)
> 
Reviewed-by: Hannes Reinecke <hare@suse.de>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke                Kernel Storage Architect
hare@suse.de                              +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Ivo Totev, Andrew
Myers, Andrew McDonald, Martje Boudien Moerman


  reply	other threads:[~2023-04-21  6:39 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21  6:04 [PATCH REPOST blktests v2 0/9] nvme testsuite runtime optimization Daniel Wagner
2023-04-21  6:04 ` [PATCH REPOST blktests v2 1/9] nvme-rc: Auto convert test device size info Daniel Wagner
2023-04-21  6:40   ` Hannes Reinecke
2023-04-28  2:39   ` Shinichiro Kawasaki
2023-04-21  6:04 ` [PATCH REPOST blktests v2 2/9] nvme: Do not hard code device size for dd test Daniel Wagner
2023-04-21  6:23   ` Hannes Reinecke
2023-04-28  2:44   ` Shinichiro Kawasaki
2023-05-02 12:54     ` Daniel Wagner
2023-04-21  6:04 ` [PATCH REPOST blktests v2 3/9] common-xfs: Make size argument optional for _xfs_run_fio_verify_io Daniel Wagner
2023-04-21  6:27   ` Hannes Reinecke
2023-04-21  6:54     ` Daniel Wagner
2023-04-28  2:54       ` Shinichiro Kawasaki
2023-05-02 13:20         ` Daniel Wagner
2023-05-02 13:19     ` Daniel Wagner
2023-04-28  2:59   ` Shinichiro Kawasaki
2023-05-02 13:23     ` Daniel Wagner
2023-05-03  4:04       ` Shinichiro Kawasaki
2023-05-03  7:29         ` Daniel Wagner
2023-04-21  6:05 ` [PATCH REPOST blktests v2 4/9] nvme: Use runtime fio background jobs Daniel Wagner
2023-04-21  6:29   ` Hannes Reinecke
2023-04-21  6:57     ` Daniel Wagner
2023-04-28  4:29       ` Shinichiro Kawasaki
2023-05-02 14:22         ` Daniel Wagner
2023-04-21  6:05 ` [PATCH REPOST blktests v2 5/9] nvme: Make test image size configurable Daniel Wagner
2023-04-21  6:31   ` Hannes Reinecke
2023-04-28  3:08   ` Shinichiro Kawasaki
2023-04-21  6:05 ` [PATCH REPOST blktests v2 6/9] nvme-rc: Add minimal test image size requirement Daniel Wagner
2023-04-21  6:31   ` Hannes Reinecke
2023-04-21  6:05 ` [PATCH REPOST blktests v2 7/9] nvme-rc: Calculate IO size for fio jobs Daniel Wagner
2023-04-21  6:33   ` Hannes Reinecke
2023-04-21  7:03     ` Daniel Wagner
2023-04-28  3:57       ` Shinichiro Kawasaki
2023-04-28  4:00   ` Shinichiro Kawasaki
2023-05-02 15:45     ` Daniel Wagner
2023-05-02 16:25       ` Daniel Wagner
2023-04-21  6:05 ` [PATCH REPOST blktests v2 8/9] nvme-rc: Move discovery generation counter code to rc Daniel Wagner
2023-04-21  6:38   ` Hannes Reinecke
2023-04-28  4:08   ` Shinichiro Kawasaki
2023-04-28  4:23   ` Shinichiro Kawasaki
2023-05-02 15:56     ` Daniel Wagner
2023-04-21  6:05 ` [PATCH REPOST blktests v2 9/9] nvme: Make the number iterations configurable Daniel Wagner
2023-04-21  6:38   ` Hannes Reinecke [this message]
2023-04-28  4:12   ` Shinichiro Kawasaki
2023-05-02 15:59     ` Daniel Wagner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c5a5cf4b-ba96-1e55-26ac-d2da9ab7117d@suse.de \
    --to=hare@suse.de \
    --cc=dwagner@suse.de \
    --cc=kch@nvidia.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=shinichiro@fastmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®