Searched hist:eec40579d84873dfb7021eb24c50360f073237c5 (Results 1 – 3 of 3) sorted by relevance
/linux/drivers/md/ |
H A D | dm-era-target.c | eec40579d84873dfb7021eb24c50360f073237c5 Mon Mar 03 16:23:15 CET 2014 Joe Thornber <ejt@redhat.com> dm: add era target
dm-era is a target that behaves similar to the linear target. In addition it keeps track of which blocks were written within a user defined period of time called an 'era'. Each era target instance maintains the current era as a monotonically increasing 32-bit counter.
Use cases include tracking changed blocks for backup software, and partially invalidating the contents of a cache to restore cache coherency after rolling back a vendor snapshot.
dm-era is primarily expected to be paired with the dm-cache target.
Signed-off-by: Joe Thornber <ejt@redhat.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com>
|
H A D | Makefile | diff eec40579d84873dfb7021eb24c50360f073237c5 Mon Mar 03 16:23:15 CET 2014 Joe Thornber <ejt@redhat.com> dm: add era target
dm-era is a target that behaves similar to the linear target. In addition it keeps track of which blocks were written within a user defined period of time called an 'era'. Each era target instance maintains the current era as a monotonically increasing 32-bit counter.
Use cases include tracking changed blocks for backup software, and partially invalidating the contents of a cache to restore cache coherency after rolling back a vendor snapshot.
dm-era is primarily expected to be paired with the dm-cache target.
Signed-off-by: Joe Thornber <ejt@redhat.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com>
|
H A D | Kconfig | diff eec40579d84873dfb7021eb24c50360f073237c5 Mon Mar 03 16:23:15 CET 2014 Joe Thornber <ejt@redhat.com> dm: add era target
dm-era is a target that behaves similar to the linear target. In addition it keeps track of which blocks were written within a user defined period of time called an 'era'. Each era target instance maintains the current era as a monotonically increasing 32-bit counter.
Use cases include tracking changed blocks for backup software, and partially invalidating the contents of a cache to restore cache coherency after rolling back a vendor snapshot.
dm-era is primarily expected to be paired with the dm-cache target.
Signed-off-by: Joe Thornber <ejt@redhat.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com>
|