From: Keith Busch <kbusch@meta.com>
To: <linux-block@vger.kernel.org>, <linux-nvme@lists.infradead.org>,
<axboe@kernel.dk>, <hch@lst.de>, <io-uring@vger.kernel.org>
Cc: <linux-fsdevel@vger.kernel.org>, <joshi.k@samsung.com>,
<javier.gonz@samsung.com>, Keith Busch <kbusch@kernel.org>
Subject: [PATCHv8 0/6] write hints for nvme fdp
Date: Thu, 17 Oct 2024 09:09:31 -0700 [thread overview]
Message-ID: <20241017160937.2283225-1-kbusch@meta.com> (raw)
From: Keith Busch <kbusch@kernel.org>
Changes from v7:
Limits io_uring per-io hints to raw block, and only if the block
device registers a new queue limit indicating support for it.
The per-io hints are opaque to the kernel.
Minor changelog and code organization changes.
I don't really understand the io_uring suggestions, so I just made the
write_hint a first class field without the "meta" indirection. It's
kind of like ioprio, which has it's own field too. Actually, might be
neat if we could use ioprio since it already has a "hints" field that
is currently only used by command duration limits.
Kanchan Joshi (3):
block, fs: restore kiocb based write hint processing
io_uring: enable per-io hinting capability
nvme: enable FDP support
Keith Busch (3):
block: use generic u16 for write hints
block: introduce max_write_hints queue limit
fs: introduce per-io hint support flag
Documentation/ABI/stable/sysfs-block | 7 +++
block/blk-settings.c | 3 +
block/blk-sysfs.c | 3 +
block/fops.c | 10 ++--
drivers/nvme/host/core.c | 82 ++++++++++++++++++++++++++++
drivers/nvme/host/nvme.h | 5 ++
fs/aio.c | 1 +
fs/cachefiles/io.c | 1 +
fs/direct-io.c | 2 +-
fs/iomap/direct-io.c | 2 +-
include/linux/blk-mq.h | 3 +-
include/linux/blk_types.h | 2 +-
include/linux/blkdev.h | 12 ++++
include/linux/fs.h | 10 ++++
include/linux/nvme.h | 19 +++++++
include/uapi/linux/io_uring.h | 4 ++
io_uring/rw.c | 10 +++-
17 files changed, 166 insertions(+), 10 deletions(-)
--
2.43.5
next reply other threads:[~2024-10-17 16:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 16:09 Keith Busch [this message]
2024-10-17 16:09 ` [PATCHv8 1/6] block, fs: restore kiocb based write hint processing Keith Busch
2024-10-18 5:50 ` Christoph Hellwig
2024-10-21 15:47 ` Keith Busch
2024-10-21 17:09 ` Bart Van Assche
2024-10-21 19:35 ` Keith Busch
2024-10-22 6:43 ` Christoph Hellwig
2024-10-22 14:37 ` Keith Busch
2024-10-22 14:40 ` Christoph Hellwig
2024-10-18 16:11 ` Bart Van Assche
2024-10-17 16:09 ` [PATCHv8 2/6] block: use generic u16 for write hints Keith Busch
2024-10-18 5:46 ` Christoph Hellwig
2024-10-24 19:45 ` Keith Busch
2024-10-25 12:20 ` Christoph Hellwig
2024-10-18 6:00 ` Hannes Reinecke
2024-10-18 16:12 ` Bart Van Assche
2024-10-21 15:03 ` Keith Busch
2024-10-17 16:09 ` [PATCHv8 3/6] block: introduce max_write_hints queue limit Keith Busch
2024-10-18 5:51 ` Christoph Hellwig
2024-10-18 6:01 ` Hannes Reinecke
2024-10-18 16:18 ` Bart Van Assche
2024-10-21 15:02 ` Keith Busch
2024-10-17 16:09 ` [PATCHv8 4/6] fs: introduce per-io hint support flag Keith Busch
2024-10-18 5:52 ` Christoph Hellwig
2024-10-18 6:03 ` Hannes Reinecke
2024-10-17 16:09 ` [PATCHv8 5/6] io_uring: enable per-io hinting capability Keith Busch
2024-10-18 5:53 ` Christoph Hellwig
2024-10-18 6:03 ` Hannes Reinecke
2024-10-17 16:09 ` [PATCHv8 6/6] nvme: enable FDP support Keith Busch
2024-10-18 10:48 ` Kanchan Joshi
2024-10-21 15:08 ` Keith Busch
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=20241017160937.2283225-1-kbusch@meta.com \
--to=kbusch@meta.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=io-uring@vger.kernel.org \
--cc=javier.gonz@samsung.com \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
/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