From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Yi Zhang <yi.zhang@redhat.com>
Cc: Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Eric Sandeen <sandeen@sandeen.net>,
"logang@deltatee.com" <logang@deltatee.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH blktests] common/xfs: ignore the 32M log size during mkfs.xfs
Date: Mon, 24 Oct 2022 10:31:52 +0000 [thread overview]
Message-ID: <20221024103151.qmfxbyysivk6uy55@shindev> (raw)
In-Reply-To: <CAHj4cs92c_3t+Ov780F5wsO_B=Mq=0T31Xhv=FWaAy=KqmXpDA@mail.gmail.com>
On Oct 24, 2022 / 14:32, Yi Zhang wrote:
> On Mon, Oct 24, 2022 at 8:50 AM Shinichiro Kawasaki
> <shinichiro.kawasaki@wdc.com> wrote:
...
> > From Yi's observation, I found a couple of improvement opportunities which are
> > beyond scope of this fix. Here I note them as memorandum (patches are welcome :)
>
> I resend the patch to set log size to 64M and another two which could
> address below :)
Thanks! I'll wait for comment by Chaitanya then review your patches.
>
> >
> > 1) Assuming nvme device size 1GB define in nvme/012 and nvme/013 has relation to
> > the fio I/O size 950m defined in common/xfs, these values should be defined
> > at single place. Probably we should define both in nvme/012 and nvme/013.
> >
> > 2) The fio I/O size 950m is defined in _xfs_run_fio_verify_io() which is called
> > from nvme/035. Then, it is implicitly assumed that TEST_DEV for nvme/035 has
> > size 1GB (or larger). I found that nvme/035 fails with 512MB nvme device.
> > We should fix this by calculating fio I/O size from TEST_DEV size. (Or
> > require 1GB nvme device size for the test case.)
> >
> > --
> > Shin'ichiro Kawasaki
> >
>
>
> --
> Best Regards,
> Yi Zhang
>
--
Shin'ichiro Kawasaki
next prev parent reply other threads:[~2022-10-24 10:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 5:12 [PATCH blktests] common/xfs: ignore the 32M log size during mkfs.xfs Yi Zhang
2022-10-19 6:06 ` Chaitanya Kulkarni
2022-10-19 6:16 ` Chaitanya Kulkarni
2022-10-19 14:19 ` Eric Sandeen
2022-10-19 19:18 ` Chaitanya Kulkarni
2022-10-21 8:58 ` Shinichiro Kawasaki
2022-10-21 21:42 ` Chaitanya Kulkarni
2022-10-21 23:56 ` Shinichiro Kawasaki
2022-10-23 15:27 ` Yi Zhang
2022-10-24 0:50 ` Shinichiro Kawasaki
2022-10-24 6:32 ` Yi Zhang
2022-10-24 10:31 ` Shinichiro Kawasaki [this message]
2022-10-25 0:42 ` Chaitanya Kulkarni
2022-10-25 1:53 ` Shinichiro Kawasaki
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=20221024103151.qmfxbyysivk6uy55@shindev \
--to=shinichiro.kawasaki@wdc.com \
--cc=chaitanyak@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=sandeen@sandeen.net \
--cc=yi.zhang@redhat.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