The patch titled
readahead: remove size limit of max_sectors_kb on read_ahead_kb
has been removed from the -mm tree. Its filename was
readahead-remove-size-limit-of-max_sectors_kb-on-read_ahead_kb.patch
This patch was dropped because an updated version will be merged
------------------------------------------------------
Subject: readahead: remove size limit of max_sectors_kb on read_ahead_kb
From: Wu Fengguang <wfg@xxxxxxxxxxxxxxxx>
Remove the correlation between max_sectors_kb and read_ahead_kb. It's
unnecessary to reduce readahead size when setting max_sectors_kb.
Signed-off-by: Wu Fengguang <wfg@xxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
block/ll_rw_blk.c | 14 --------------
1 file changed, 14 deletions(-)
diff -puN block/ll_rw_blk.c~readahead-remove-size-limit-of-max_sectors_kb-on-read_ahead_kb block/ll_rw_blk.c
--- a/block/ll_rw_blk.c~readahead-remove-size-limit-of-max_sectors_kb-on-read_ahead_kb
+++ a/block/ll_rw_blk.c
@@ -3913,25 +3913,11 @@ queue_max_sectors_store(struct request_q
max_hw_sectors_kb = q->max_hw_sectors >> 1,
page_kb = 1 << (PAGE_CACHE_SHIFT - 10);
ssize_t ret = queue_var_store(&max_sectors_kb, page, count);
- int ra_kb;
if (max_sectors_kb > max_hw_sectors_kb || max_sectors_kb < page_kb)
return -EINVAL;
- /*
- * Take the queue lock to update the readahead and max_sectors
- * values synchronously:
- */
- spin_lock_irq(q->queue_lock);
- /*
- * Trim readahead window as well, if necessary:
- */
- ra_kb = q->backing_dev_info.ra_pages << (PAGE_CACHE_SHIFT - 10);
- if (ra_kb > max_sectors_kb)
- q->backing_dev_info.ra_pages =
- max_sectors_kb >> (PAGE_CACHE_SHIFT - 10);
q->max_sectors = max_sectors_kb << 1;
- spin_unlock_irq(q->queue_lock);
return ret;
}
_
Patches currently in -mm which might be from wfg@xxxxxxxxxxxxxxxx are
origin.patch
readahead-remove-size-limit-of-max_sectors_kb-on-read_ahead_kb.patch
readahead-partial-sendfile-fix.patch
readahead-turn-on-by-default.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
