All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: shinichiro.kawasaki@wdc.com
Cc: linux-block@vger.kernel.org, hare@suse.de,
	patches@lists.linux.dev, gost.dev@samsung.com, mcgrof@kernel.org
Subject: [PATCH blktests 0/4] enable bs > ps device testing
Date: Wed, 18 Dec 2024 03:21:49 -0800	[thread overview]
Message-ID: <20241218112153.3917518-1-mcgrof@kernel.org> (raw)

As we move forward with bs > ps block device support, add blktests support
for these devices. This leverages min-io so to also ensure we make the IOs
optimal and make a uniform way to get this min-io from a file or block device.

Luis Chamberlain (4):
  common: add and use min io for fio
  common/xfs: use min io for fs blocksize
  tests: use test device min io to support bs > ps
  nvme/053: provide time extension alternative

 common/fio      |  6 ++++--
 common/rc       | 10 ++++++++++
 common/xfs      |  8 +++++++-
 tests/block/003 |  4 +++-
 tests/block/007 |  3 ++-
 tests/nvme/049  |  5 +++--
 tests/nvme/053  | 11 ++++++-----
 7 files changed, 35 insertions(+), 12 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-12-18 11:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-18 11:21 Luis Chamberlain [this message]
2024-12-18 11:21 ` [PATCH blktests 1/4] common: add and use min io for fio Luis Chamberlain
2024-12-23  9:37   ` Shinichiro Kawasaki
2025-01-04  4:10     ` Luis Chamberlain
2025-01-07  5:19       ` Shinichiro Kawasaki
2025-02-04 19:06         ` Luis Chamberlain
2024-12-18 11:21 ` [PATCH blktests 2/4] common/xfs: use min io for fs blocksize Luis Chamberlain
2024-12-18 11:21 ` [PATCH blktests 3/4] tests: use test device min io to support bs > ps Luis Chamberlain
2024-12-18 11:21 ` [PATCH blktests 4/4] nvme/053: provide time extension alternative Luis Chamberlain

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=20241218112153.3917518-1-mcgrof@kernel.org \
    --to=mcgrof@kernel.org \
    --cc=gost.dev@samsung.com \
    --cc=hare@suse.de \
    --cc=linux-block@vger.kernel.org \
    --cc=patches@lists.linux.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.