[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <clh6gmnivvi5e4o7pzr3mxfale3vlymgepdntkjtvub4cazyvk@myovldb6bcnx>
Date: Tue, 2 May 2023 15:23:05 +0200
From: Daniel Wagner <dwagner@...e.de>
To: Shinichiro Kawasaki <shinichiro.kawasaki@....com>
Cc: "linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
Chaitanya Kulkarni <kch@...dia.com>,
Shin'ichiro Kawasaki <shinichiro@...tmail.com>
Subject: Re: [PATCH REPOST blktests v2 3/9] common-xfs: Make size argument
optional for _xfs_run_fio_verify_io
> --- a/tests/nvme/035
> > +++ b/tests/nvme/035
> > @@ -32,7 +32,7 @@ test_device() {
> > port=$(_nvmet_passthru_target_setup "${subsys}")
> > nsdev=$(_nvmet_passthru_target_connect "${nvme_trtype}" "${subsys}")
> >
> > - _xfs_run_fio_verify_io "${nsdev}" "900m"
> > + _xfs_run_fio_verify_io "${nsdev}"
>
> On the other hand, this change for nvme/035 does not look good. It runs the
> test on TEST_DEV, which may take very long time without TIMEOUT config.
I'll add the nvme_img_size argument here instead (nvme: Make test image size
configurable)
Powered by blists - more mailing lists