From: Yi Zhang <yi.zhang@redhat.com>
To: shinichiro.kawasaki@wdc.com
Cc: chaitanyak@nvidia.com, linux-block@vger.kernel.org
Subject: [PATCH V2 blktests 0/3] fix and improvement for xfs log size change from new xfsprogs version
Date: Wed, 2 Nov 2022 10:56:59 +0800 [thread overview]
Message-ID: <20221102025702.1664101-1-yi.zhang@redhat.com> (raw)
Hi
The first patch addressed nvme/012 nvme/013 failure which introduced
from xfsprogs v5.19.0, the minimun xfs log size change to 64m
The second patch introduced one new function _require_test_dev_size_mb
The third patch add one new parameter to _run_fio_verify_io, this will
allow fio I/O size definition to the test case
V2:
Update the new function to _require_test_dev_size_mb and nvme/035
to call it for test dev size checking for the second patch
Update the title and description for better reflect the change for the
third patch
V1: https://lore.kernel.org/linux-block/20221024061319.1133470-1-yi.zhang@redhat.com/
Yi Zhang (3):
common/xfs: set the minimal log size 64m during mkfs.xfs
common/rc: add one function _require_test_dev_size_mb
nvme/012,013,035: change fio I/O size and move size definition place
common/rc | 10 ++++++++++
common/xfs | 5 +++--
tests/nvme/012 | 2 +-
tests/nvme/013 | 2 +-
tests/nvme/035 | 6 +++++-
5 files changed, 20 insertions(+), 5 deletions(-)
--
2.34.1
next reply other threads:[~2022-11-02 2:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 2:56 Yi Zhang [this message]
2022-11-02 2:57 ` [PATCH V2 blktests 1/3] common/xfs: set the minimal log size 64m during mkfs.xfs Yi Zhang
2022-11-02 2:57 ` [PATCH V2 blktests 2/3] common/rc: add one function to check required dev size for TEST_DEV Yi Zhang
2022-11-02 2:57 ` [PATCH V2 blktests 3/3] nvme/012,013,035: change fio I/O size and move size definition place Yi Zhang
2022-11-02 5:43 ` [PATCH V2 blktests 0/3] fix and improvement for xfs log size change from new xfsprogs version Chaitanya Kulkarni
2022-11-04 11:42 ` 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=20221102025702.1664101-1-yi.zhang@redhat.com \
--to=yi.zhang@redhat.com \
--cc=chaitanyak@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.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;
as well as URLs for NNTP newsgroup(s).