[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4ckg7ymu73lfs7zlsby3com6k24qgovkaqky5jmgeoubs7azhh@jtvovyjluekv>
Date: Fri, 21 Apr 2023 08:57:43 +0200
From: Daniel Wagner <dwagner@...e.de>
To: Hannes Reinecke <hare@...e.de>
Cc: linux-nvme@...ts.infradead.org, linux-kernel@...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 4/9] nvme: Use runtime fio background
jobs
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.
Powered by blists - more mailing lists