| commit | 84890c03b6c5d7e8d76ea5e20b6aaf7e7ad410f0 | |
| author | Shaohua Li <shli@fb.com> | |
| Thu, 16 Feb 2017 03:58:05 +0000 (15 19:58 -0800) | ||
| committer | Shaohua Li <shli@fb.com> | |
| Thu, 16 Mar 2017 23:55:51 +0000 (16 16:55 -0700) | ||
| tree | 68faa6589a2f76235444403cbef5ebb7d55ad157 | treesnapshot (tar.gz zip) |
| parent | 535ae4eb1225f19e1d1848c65eafea8b7e9112f4 | commitdiff |
md/raid5-cache: bump flush stripe batch size
Bump the flush stripe batch size to 2048. For my 12 disks raid
array, the stripes takes:
12 * 4k * 2048 = 96MB
This is still quite small. A hardware raid card generally has 1GB size,
which we suggest the raid5-cache has similar cache size.
The advantage of a big batch size is we can dispatch a lot of IO in the
same time, then we can do some scheduling to make better IO pattern.
Last patch prioritizes stripes, so we don't worry about a big flush
stripe batch will starve normal stripes.
Signed-off-by: Shaohua Li <shli@fb.com>
Bump the flush stripe batch size to 2048. For my 12 disks raid
array, the stripes takes:
12 * 4k * 2048 = 96MB
This is still quite small. A hardware raid card generally has 1GB size,
which we suggest the raid5-cache has similar cache size.
The advantage of a big batch size is we can dispatch a lot of IO in the
same time, then we can do some scheduling to make better IO pattern.
Last patch prioritizes stripes, so we don't worry about a big flush
stripe batch will starve normal stripes.
Signed-off-by: Shaohua Li <shli@fb.com>
| drivers/md/raid5-cache.c | diffblobblamehistory |