From: Keith Busch <kbusch@meta.com>
To: <axboe@kernel.dk>, <hch@lst.de>, <linux-block@vger.kernel.org>,
<linux-nvme@lists.infradead.org>, <linux-fsdevel@vger.kernel.org>,
<io-uring@vger.kernel.org>
Cc: <sagi@grimberg.me>, <asml.silence@gmail.com>,
<anuj20.g@samsung.com>, <joshi.k@samsung.com>,
Keith Busch <kbusch@kernel.org>
Subject: [PATCHv13 00/11] block write streams with nvme fdp
Date: Tue, 10 Dec 2024 11:47:11 -0800 [thread overview]
Message-ID: <20241210194722.1905732-1-kbusch@meta.com> (raw)
From: Keith Busch <kbusch@kernel.org>
Previous discussion threads:
v12: https://lore.kernel.org/linux-nvme/20241206221801.790690-1-kbusch@meta.com/T/#u
v11: https://lore.kernel.org/linux-nvme/20241206015308.3342386-1-kbusch@meta.com/T/#u
Changes from v12:
- Removed statx. We need additional time to consider the best way to
expose these attributes. Until then, applications can fallback to the
sysfs block attribute to query write stream settings.
- More verbose logging on error.
- Added reviews.
- Explicitly clear the return value to 0 for unsupported or
unrecognized FDP configs; while it's not technically needed (it's
already 0 in these paths), it makes it clear that a non-error return
wasn't an accidental oversight.
- Fixed the compiler warnings from unitialized variable; switched the
do-while to a more clear for-loop.
- Fixed long-line wrapping
- Memory leak when cleaning up the namespace head.
- Don't rescan FDP configuration if we successfully set it up before.
The namespaces' FDP configuration is static.
- Better function name querying the size granularity of the FDP reclaim
unit.
Christoph Hellwig (7):
fs: add a write stream field to the kiocb
block: add a bi_write_stream field
block: introduce a write_stream_granularity queue limit
block: expose write streams for block device nodes
nvme: add a nvme_get_log_lsi helper
nvme: pass a void pointer to nvme_get/set_features for the result
nvme: add FDP definitions
Keith Busch (4):
block: introduce max_write_streams queue limit
io_uring: enable per-io write streams
nvme: register fdp parameters with the block layer
nvme: use fdp streams if write stream is provided
Documentation/ABI/stable/sysfs-block | 15 +++
block/bio.c | 2 +
block/blk-crypto-fallback.c | 1 +
block/blk-merge.c | 4 +
block/blk-sysfs.c | 6 +
block/bounce.c | 1 +
block/fops.c | 23 ++++
drivers/nvme/host/core.c | 186 ++++++++++++++++++++++++++-
drivers/nvme/host/nvme.h | 7 +-
include/linux/blk_types.h | 1 +
include/linux/blkdev.h | 16 +++
include/linux/fs.h | 1 +
include/linux/nvme.h | 77 +++++++++++
include/uapi/linux/io_uring.h | 4 +
io_uring/io_uring.c | 2 +
io_uring/rw.c | 1 +
16 files changed, 341 insertions(+), 6 deletions(-)
--
2.43.5
next reply other threads:[~2024-12-10 20:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 19:47 Keith Busch [this message]
2024-12-10 19:47 ` [PATCHv13 01/11] fs: add a write stream field to the kiocb Keith Busch
2024-12-10 19:47 ` [PATCHv13 02/11] block: add a bi_write_stream field Keith Busch
2024-12-10 19:47 ` [PATCHv13 03/11] block: introduce max_write_streams queue limit Keith Busch
2024-12-10 19:47 ` [PATCHv13 04/11] block: introduce a write_stream_granularity " Keith Busch
2024-12-11 8:46 ` John Garry
2024-12-10 19:47 ` [PATCHv13 05/11] block: expose write streams for block device nodes Keith Busch
2024-12-11 5:53 ` Nitesh Shetty
2024-12-10 19:47 ` [PATCHv13 06/11] io_uring: enable per-io write streams Keith Busch
2024-12-11 6:44 ` Nitesh Shetty
2024-12-10 19:47 ` [PATCHv13 07/11] nvme: add a nvme_get_log_lsi helper Keith Busch
2024-12-10 19:47 ` [PATCHv13 08/11] nvme: pass a void pointer to nvme_get/set_features for the result Keith Busch
2024-12-10 19:47 ` [PATCHv13 09/11] nvme: add FDP definitions Keith Busch
2024-12-10 19:47 ` [PATCHv13 10/11] nvme: register fdp parameters with the block layer Keith Busch
2024-12-11 6:41 ` Nitesh Shetty
2024-12-11 9:30 ` John Garry
2024-12-11 15:55 ` Keith Busch
2024-12-11 11:23 ` Hannes Reinecke
2024-12-11 14:40 ` kernel test robot
2024-12-11 17:18 ` kernel test robot
2024-12-10 19:47 ` [PATCHv13 11/11] nvme: use fdp streams if write stream is provided Keith Busch
2024-12-11 7:13 ` [PATCHv13 00/11] block write streams with nvme fdp Christoph Hellwig
2024-12-12 5:51 ` Kanchan Joshi
2024-12-12 6:05 ` Christoph Hellwig
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=20241210194722.1905732-1-kbusch@meta.com \
--to=kbusch@meta.com \
--cc=anuj20.g@samsung.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=io-uring@vger.kernel.org \
--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=sagi@grimberg.me \
/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