linux/drivers/md/persistent-data
Joe Thornber b0988900ba dm persistent data: fix btree rebalancing after remove
When we remove an entry from a node we sometimes rebalance with it's
two neighbours.  This wasn't being done correctly; in some cases
entries have to move all the way from the right neighbour to the left
neighbour, or vice versa.  This patch pretty much re-writes the
balancing code to fix it.

This code is barely used currently; only when you delete a thin
device, and then only if you have hundreds of them in the same pool.
Once we have discard support, which removes mappings, this will be used
much more heavily.

Signed-off-by: Joe Thornber <ejt@redhat.com>
Cc: stable@kernel.org
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: Alasdair G Kergon <agk@redhat.com>
2012-03-28 18:41:23 +01:00
..
Kconfig
Makefile
dm-block-manager.c
dm-block-manager.h
dm-btree-internal.h
dm-btree-remove.c dm persistent data: fix btree rebalancing after remove 2012-03-28 18:41:23 +01:00
dm-btree-spine.c
dm-btree.c
dm-btree.h
dm-persistent-data-internal.h
dm-space-map-checker.c device-mapper: using EXPORT_SYBOL in dm-space-map-checker.c needs export.h 2011-11-07 10:29:10 -08:00
dm-space-map-checker.h
dm-space-map-common.c
dm-space-map-common.h
dm-space-map-disk.c
dm-space-map-disk.h
dm-space-map-metadata.c
dm-space-map-metadata.h
dm-space-map.h
dm-transaction-manager.c
dm-transaction-manager.h