From: Keith Busch <kbusch@meta.com>
To: <linux-block@vger.kernel.org>, <linux-nvme@lists.infradead.org>,
<linux-scsi@vger.kernel.org>, <io-uring@vger.kernel.org>
Cc: <linux-fsdevel@vger.kernel.org>, <hch@lst.de>,
<joshi.k@samsung.com>, <javier.gonz@samsung.com>,
<bvanassche@acm.org>, Keith Busch <kbusch@kernel.org>
Subject: [PATCHv9 0/7] write hints with nvme fdp, scsi streams
Date: Fri, 25 Oct 2024 14:36:38 -0700 [thread overview]
Message-ID: <20241025213645.3464331-1-kbusch@meta.com> (raw)
From: Keith Busch <kbusch@kernel.org>
A little something for everyone here.
Upfront, I really didn't get the feedback about setting different flags
for stream vs. temperature support. Who wants to use it, and where and
how is that information used?
Changes from v8:
Added reviews.
Removed an unused header.
Changed "hint" to "streams" in the commit logs.
Ability to split available hints that a partition can use.
Dropped all the generic filesystem changes that were defaulting to the
kiocb write_hint. They are unchanged, which having no functional
change was really the intention anyway, so let's just not change them.
The above means we don't need a special fop flag to indicate support
for the kiocb write_hint. Those filesystems that don't support it
simply don't read it.
Added the SCSI support since I had to read the spec anyway, and it is
just a one-line change.
Kanchan Joshi (2):
io_uring: enable per-io hinting capability
nvme: enable FDP support
Keith Busch (5):
block: use generic u16 for write hints
block: introduce max_write_hints queue limit
block: allow ability to limit partition write hints
block, fs: add write hint to kiocb
scsi: set permanent stream count in block limits
Documentation/ABI/stable/sysfs-block | 7 +++
block/bdev.c | 15 +++++
block/blk-settings.c | 3 +
block/blk-sysfs.c | 3 +
block/fops.c | 26 ++++++++-
block/partitions/core.c | 46 +++++++++++++++-
drivers/nvme/host/core.c | 82 ++++++++++++++++++++++++++++
drivers/nvme/host/nvme.h | 5 ++
drivers/scsi/sd.c | 2 +
include/linux/blk-mq.h | 3 +-
include/linux/blk_types.h | 4 +-
include/linux/blkdev.h | 12 ++++
include/linux/fs.h | 1 +
include/linux/nvme.h | 19 +++++++
include/uapi/linux/io_uring.h | 4 ++
io_uring/rw.c | 3 +-
16 files changed, 225 insertions(+), 10 deletions(-)
--
2.43.5
next reply other threads:[~2024-10-25 21:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 21:36 Keith Busch [this message]
2024-10-25 21:36 ` [PATCHv9 3/7] block: allow ability to limit partition write hints Keith Busch
2024-10-28 11:58 ` Christoph Hellwig
2024-10-28 14:49 ` Keith Busch
2024-10-28 14:40 ` Kanchan Joshi
2024-10-28 18:27 ` Bart Van Assche
2024-10-28 19:46 ` Keith Busch
2024-10-25 21:36 ` [PATCHv9 4/7] block, fs: add write hint to kiocb Keith Busch
2024-10-28 11:59 ` Christoph Hellwig
2024-10-28 14:38 ` Keith Busch
2024-10-28 16:08 ` Christoph Hellwig
2024-10-25 21:36 ` [PATCHv9 7/7] scsi: set permanent stream count in block limits Keith Busch
2024-10-28 16:13 ` Bart Van Assche
2024-10-29 7:10 ` Hannes Reinecke
2024-10-28 11:49 ` [PATCHv9 0/7] write hints with nvme fdp, scsi streams Christoph Hellwig
[not found] ` <20241025213645.3464331-3-kbusch@meta.com>
2024-10-28 11:51 ` [PATCHv9 2/7] block: introduce max_write_hints queue limit Christoph Hellwig
2024-10-28 11:52 ` Christoph Hellwig
[not found] ` <20241025213645.3464331-2-kbusch@meta.com>
2024-10-28 18:19 ` [PATCHv9 1/7] block: use generic u16 for write hints Bart Van Assche
2024-10-28 18:38 ` Keith Busch
[not found] ` <20241025213645.3464331-6-kbusch@meta.com>
2024-10-29 12:46 ` [PATCHv9 5/7] io_uring: enable per-io hinting capability Anuj gupta
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=20241025213645.3464331-1-kbusch@meta.com \
--to=kbusch@meta.com \
--cc=bvanassche@acm.org \
--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 \
--cc=linux-scsi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).