From: "Theodore Ts'o" <tytso@mit.edu>
To: "Luís Henriques" <lhenriques@suse.de>
Cc: fstests@vger.kernel.org, Ming Lei <ming.lei@redhat.com>,
Zorro Lang <zlang@redhat.com>, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH] generic/095: don't use 1k blocksize for DIO operations
Date: Mon, 11 Oct 2021 10:36:34 -0400 [thread overview]
Message-ID: <YWRL8pftnuS/iASr@mit.edu> (raw)
In-Reply-To: <20211011135504.23328-1-lhenriques@suse.de>
On Mon, Oct 11, 2021 at 02:55:04PM +0100, Luís Henriques wrote:
> This test fails when using zram because it's using bs=1k for DIO in fio
> jobs. Fix the test by using _min_dio_alignment instead to get the correct
> blocksize.
>
> Signed-off-by: Luís Henriques <lhenriques@suse.de>
I'd suggest using the commit summary:
generic/095: align DIO read/writes with the supported sector size for the device
It might also be worth noting that generic/095 would have been failing
not just for zram, but if run on other hardware devices that might
have a logical sector size > 1k --- e.g., advanced format HDD's with
4k sectors, DASD's on mainframes with 2k sectors, etc.
Note: this change will cause the fio stress workload to do its DIO
operations using a block size of 512, which I think is fine for this
test. (There might be other tests which are making assumptions about
the supported DIO alignment of the scratch device where adjusting the
test might be more complicated; fortunately, this doesn't appear to be
one of them.)
Other than changes to the commit description, feel free to add:
Reviewed-by: Theodore Ts'o <tytso@mit.edu>
Thanks,
- Ted
prev parent reply other threads:[~2021-10-11 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 13:55 [PATCH] generic/095: don't use 1k blocksize for DIO operations Luís Henriques
2021-10-11 14:36 ` Theodore Ts'o [this message]
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=YWRL8pftnuS/iASr@mit.edu \
--to=tytso@mit.edu \
--cc=axboe@kernel.dk \
--cc=fstests@vger.kernel.org \
--cc=lhenriques@suse.de \
--cc=ming.lei@redhat.com \
--cc=zlang@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