diff options
| author | Keith Busch <kbusch@kernel.org> | 2025-10-20 13:47:15 -0700 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2025-10-22 07:39:39 -0600 |
| commit | 5c5028ee594ce5f907ca6ad1c32cca6a15098464 (patch) | |
| tree | 1885cf9a72cb20586df9506bec8d08c57926f42a /block/blk-merge.c | |
| parent | e5a82249d88c7063c4ac998704b0ae5784013976 (diff) | |
block: rename min_segment_size
Despite its name, the block layer is fine with segments smaller that the
"min_segment_size" limit. The value is an optimization limit indicating
the largest segment that can be used without considering boundary
limits. Smaller segments can take a fast path, so give it a name that
reflects that: max_fast_segment_size.
Signed-off-by: Keith Busch <kbusch@kernel.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Ming Lei <ming.lei@redhat.com>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block/blk-merge.c')
| -rw-r--r-- | block/blk-merge.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/block/blk-merge.c b/block/blk-merge.c index 37864c5d287e..c47d18587a0b 100644 --- a/block/blk-merge.c +++ b/block/blk-merge.c @@ -336,7 +336,7 @@ int bio_split_io_at(struct bio *bio, const struct queue_limits *lim, if (nsegs < lim->max_segments && bytes + bv.bv_len <= max_bytes && - bv.bv_offset + bv.bv_len <= lim->min_segment_size) { + bv.bv_offset + bv.bv_len <= lim->max_fast_segment_size) { nsegs++; bytes += bv.bv_len; } else { |