diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2022-03-26 11:51:46 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2022-03-26 11:51:46 -0700 |
| commit | 561593a048d7d6915889706f4b503a65435c033a (patch) | |
| tree | 5b802be4953a1dae421b528d32082e297a17a7cc /fs/mpage.c | |
| parent | 9bf3fc5007856d5ca76d6e7a4652e3b67b683241 (diff) | |
| parent | 7b12e49669c99f63bc12351c57e581f1f14d4adf (diff) | |
Merge tag 'for-5.18/write-streams-2022-03-18' of git://git.kernel.dk/linux-block
Pull NVMe write streams removal from Jens Axboe:
"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"
* tag 'for-5.18/write-streams-2022-03-18' of git://git.kernel.dk/linux-block:
fs: remove fs.f_write_hint
fs: remove kiocb.ki_hint
block: remove the per-bio/request write hint
nvme: remove support or stream based temperature hint
Diffstat (limited to 'fs/mpage.c')
| -rw-r--r-- | fs/mpage.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/fs/mpage.c b/fs/mpage.c index 9ed1e58e8d70..3e18c6e82e60 100644 --- a/fs/mpage.c +++ b/fs/mpage.c @@ -588,7 +588,6 @@ alloc_new: GFP_NOFS); bio->bi_iter.bi_sector = blocks[0] << (blkbits - 9); wbc_init_bio(wbc, bio); - bio->bi_write_hint = inode->i_write_hint; } /* |