From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: [GIT PULL] Remove write streams support
Date: Fri, 25 Mar 2022 09:08:59 -0600 [thread overview]
Message-ID: <72c1ee9c-2abb-3ee7-7511-e6d972f4413f@kernel.dk> (raw)
Hi Linus,
This removes the write streams support in NVMe. No vendor ever really
shipped working support for this, and they are not interested in
supporting it.
With the NVMe support gone, we have nothing in the tree that supports
this. Remove passing around of the hints.
The only discussion point in this patchset imho is the fact that the
file specific write hint setting/getting fcntl helpers will now return
-1/EINVAL like they did before we supported write hints. No known
applications use these functions, I only know of one prototype that I
help do for RocksDB, and that's not used. That said, with a change like
this, it's always a bit controversial. Alternatively, we could just make
them return 0 and pretend it worked. It's placement based hints after
all.
Diffstat manually generated, as git pull-request doesn't like that it's
based on merges. It will merge cleanly with your current tree.
Please pull!
The following changes since commit 97939610b893de068c82c347d06319cd231a4602:
block: remove bio_devname (2022-03-07 06:42:33 -0700)
are available in the Git repository at:
git://git.kernel.dk/linux-block.git tags/for-5.18/write-streams-2022-03-18
for you to fetch changes up to 7b12e49669c99f63bc12351c57e581f1f14d4adf:
fs: remove fs.f_write_hint (2022-03-08 17:55:03 -0700)
----------------------------------------------------------------
for-5.18/write-streams-2022-03-18
----------------------------------------------------------------
Christoph Hellwig (4):
nvme: remove support or stream based temperature hint
block: remove the per-bio/request write hint
fs: remove kiocb.ki_hint
fs: remove fs.f_write_hint
Jens Axboe (3):
Merge branch 'for-5.18/block' into for-5.18/write-streams
Merge branch 'for-5.18/drivers' into for-5.18/write-streams
Merge branch 'for-5.18/alloc-cleanups' into for-5.18/write-streams
block/bio.c | 2 -
block/blk-crypto-fallback.c | 1 -
block/blk-merge.c | 14 -----
block/blk-mq-debugfs.c | 24 --------
block/blk-mq.c | 1 -
block/bounce.c | 1 -
block/fops.c | 3 -
drivers/md/raid1.c | 2 -
drivers/md/raid5-ppl.c | 28 +---------
drivers/md/raid5.c | 6 --
drivers/nvme/host/core.c | 143 -----------------------------------------------
drivers/nvme/host/nvme.h | 1 -
fs/aio.c | 1 -
fs/btrfs/extent_io.c | 1 -
fs/buffer.c | 13 ++---
fs/cachefiles/io.c | 2 -
fs/direct-io.c | 3 -
fs/ext4/page-io.c | 5 +-
fs/f2fs/data.c | 2 -
fs/f2fs/file.c | 6 --
fs/fcntl.c | 18 ------
fs/gfs2/lops.c | 1 -
fs/io_uring.c | 1 -
fs/iomap/buffered-io.c | 2 -
fs/iomap/direct-io.c | 1 -
fs/mpage.c | 1 -
fs/open.c | 1 -
fs/zonefs/super.c | 1 -
include/linux/blk_types.h | 1 -
include/linux/blkdev.h | 3 -
include/linux/fs.h | 21 -------
include/trace/events/f2fs.h | 3 +-
32 files changed, 10 insertions(+), 303 deletions(-)
--
Jens Axboe
next reply other threads:[~2022-03-25 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 15:08 Jens Axboe [this message]
2022-03-26 20:18 ` [GIT PULL] Remove write streams support pr-tracker-bot
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=72c1ee9c-2abb-3ee7-7511-e6d972f4413f@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).