17 Jan, 2014
1 commit
-
The cache's policy may have been established using the "default" alias,
which is currently the "mq" policy but the default policy may change in
the future. It is useful to know exactly which policy is being used.Add a 'real' member to the dm_cache_policy_type structure and have the
"default" dm_cache_policy_type point to the real "mq"
dm_cache_policy_type. Update dm_cache_policy_get_name() to check if
real is set, if so report the name of the real policy (not the alias).Requested-by: Jonathan Brassow
Signed-off-by: Mike Snitzer
12 Nov, 2013
1 commit
-
Implement policy_remove_cblock() and add remove_cblock method to the mq
policy. These methods will be used by the following cache block
invalidation patch which adds the 'invalidate_cblocks' message to the
cache core.Also, update some comments in dm-cache-policy.h
Signed-off-by: Joe Thornber
Signed-off-by: Mike Snitzer
10 May, 2013
1 commit
-
Correct the documented requirement on the return code from dm cache policy
lookup functions stated in the policy module header file.Signed-off-by: Alasdair G Kergon
21 Mar, 2013
1 commit
-
Separate dm cache policy version string into 3 unsigned numbers
corresponding to major, minor and patchlevel and store them at the end
of the on-disk metadata so we know which version of the policy generated
the hints in case a future version wants to use them differently.Signed-off-by: Mike Snitzer
Signed-off-by: Alasdair G Kergon
02 Mar, 2013
1 commit
-
Add a target that allows a fast device such as an SSD to be used as a
cache for a slower device such as a disk.A plug-in architecture was chosen so that the decisions about which data
to migrate and when are delegated to interchangeable tunable policy
modules. The first general purpose module we have developed, called
"mq" (multiqueue), follows in the next patch. Other modules are
under development.Signed-off-by: Joe Thornber
Signed-off-by: Heinz Mauelshagen
Signed-off-by: Mike Snitzer
Signed-off-by: Alasdair G Kergon