diff options
author | Christoph Hellwig <[email protected]> | 2024-06-27 14:49:11 +0200 |
---|---|---|
committer | Jens Axboe <[email protected]> | 2024-06-28 10:37:34 -0600 |
commit | 667ea36378cf7f669044b27871c496e1559c872a (patch) | |
tree | 3f08fd89c72818d36a042939889fd580cab4cbc0 /lib/test_fortify/write_overflow-strncpy-src.c | |
parent | 0676c434a99be42f3bacca4adfd27df65edbf903 (diff) |
loop: don't set QUEUE_FLAG_NOMERGES
QUEUE_FLAG_NOMERGES isn't really a driver interface, but a user tunable.
There also isn't any good reason to set it in the loop driver.
The original commit adding it (5b5e20f421c0b6d "block: loop: set
QUEUE_FLAG_NOMERGES for request queue of loop") claims that "It doesn't
make sense to enable merge because the I/O submitted to backing file is
handled page by page." which of course isn't true for multi-page bvec
now, and it never has been for direct I/O, for which commit 40326d8a33d
("block/loop: allow request merge for directio mode") alredy disabled
the nomerges flag.
Signed-off-by: Christoph Hellwig <[email protected]>
Reviewed-by: Bart Van Assche <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions