diff options
author | NeilBrown <neilb@suse.de> | 2009-03-31 07:27:02 +0400 |
---|---|---|
committer | NeilBrown <neilb@suse.de> | 2009-03-31 07:27:02 +0400 |
commit | 1187cf0a3c8b647d08bc86e043563c8d2a327adc (patch) | |
tree | 759515a3fdcbf962f35255f90ea6c4d7c708391a /drivers/md/linear.c | |
parent | eea1bf384e05b5ab747f8530c4fba9e9e6907fff (diff) | |
download | linux-1187cf0a3c8b647d08bc86e043563c8d2a327adc.tar.xz |
md: Allow write-intent bitmaps to have chunksize < PAGE_SIZE
md currently insists that the chunk size used for write-intent
bitmaps (the amount of data that corresponds to one chunk)
be at least one page.
The reason for this restriction is lost in the mists of time,
but a review of the code (and a vague memory) suggests that the only
problem would be related to resync. Resync tries very hard to
work in multiples of a page, but also needs to sync with units
of a bitmap_chunk too.
This connection comes out in the bitmap_start_sync call.
So change bitmap_start_sync to always work in multiples of a page.
If the bitmap chunk size is less that one page, we flag multiple
chunks as 'syncing' and generally make them all appear to the
resync routines like one chunk.
All other code either already works with data ranges that could
span multiple chunks, or explicitly only cares about a single chunk.
Signed-off-by: Neil Brown <neilb@suse.de>
Diffstat (limited to 'drivers/md/linear.c')
0 files changed, 0 insertions, 0 deletions