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 5/9] nvme: Make test image size configurable
Date: Fri, 21 Apr 2023 08:31:15 +0200 [thread overview]
Message-ID: <1b0b700c-7138-0324-dd95-e56fc0e8d04b@suse.de> (raw)
In-Reply-To: <20230421060505.10132-6-dwagner@suse.de>
On 4/21/23 08:05, Daniel Wagner wrote:
> The reduce the overall runtime of the testsuite by making the default
> size of the test image small. For verification jobs, the default can be
> overwriten via the newly introduced nvme_img_size environment variable.
>
> The default size of 350M is the minimum requirement of nvme/012 and
> nvme/013. These tests rely on an xfs filesystem which requires this
> minimum size.
>
> Signed-off-by: Daniel Wagner <dwagner@suse.de>
> ---
> tests/nvme/004 | 2 +-
> tests/nvme/005 | 2 +-
> tests/nvme/006 | 2 +-
> tests/nvme/007 | 2 +-
> tests/nvme/008 | 2 +-
> tests/nvme/009 | 2 +-
> tests/nvme/010 | 5 +++--
> tests/nvme/011 | 5 +++--
> tests/nvme/012 | 2 +-
> tests/nvme/013 | 2 +-
> tests/nvme/014 | 2 +-
> tests/nvme/015 | 2 +-
> tests/nvme/017 | 2 +-
> tests/nvme/018 | 2 +-
> tests/nvme/019 | 2 +-
> tests/nvme/020 | 2 +-
> tests/nvme/021 | 2 +-
> tests/nvme/022 | 2 +-
> tests/nvme/023 | 2 +-
> tests/nvme/024 | 2 +-
> tests/nvme/025 | 2 +-
> tests/nvme/026 | 2 +-
> tests/nvme/027 | 2 +-
> tests/nvme/028 | 2 +-
> tests/nvme/029 | 3 ++-
> tests/nvme/031 | 2 +-
> tests/nvme/032 | 2 +-
> tests/nvme/034 | 2 +-
> tests/nvme/035 | 2 +-
> tests/nvme/040 | 4 ++--
> tests/nvme/041 | 2 +-
> tests/nvme/042 | 2 +-
> tests/nvme/043 | 2 +-
> tests/nvme/044 | 2 +-
> tests/nvme/045 | 2 +-
> tests/nvme/047 | 2 +-
> tests/nvme/048 | 2 +-
> tests/nvme/rc | 1 +
> 38 files changed, 44 insertions(+), 40 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
next prev parent reply other threads:[~2023-04-21 6:31 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 [this message]
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
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=1b0b700c-7138-0324-dd95-e56fc0e8d04b@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®