linux-toradex.git/drivers/md/dm-cache-background-tracker.c, branch v5.5-rc7

dm cache background tracker: fix sparse warning

2018-04-30T19:40:40+00:00

Fix drivers/md/dm-cache-background-tracker.c:169:16: warning: symbol
'alloc_work' was not declared. Should it be static?

Signed-off-by: Mike Snitzer

dm cache background tracker: limit amount of background work that may be issued at once

2017-11-10T20:45:03+00:00

On large systems the cache policy can be over enthusiastic and queue far
too much dirty data to be written back.  This consumes memory.

Signed-off-by: Joe Thornber 
Signed-off-by: Mike Snitzer

dm cache: handle kmalloc failure allocating background_tracker struct

2017-05-17T13:44:53+00:00

Currently there is no kmalloc failure check on the allocation of
the background_tracker struct in btracker_create(), and so a NULL return
will lead to a NULL pointer dereference.  Add a NULL check.

Detected by CoverityScan, CID#1416587 ("Dereference null return value")

Fixes: b29d4986d ("dm cache: significant rework to leverage dm-bio-prison-v2")
Signed-off-by: Colin Ian King 
Signed-off-by: Mike Snitzer

dm cache: significant rework to leverage dm-bio-prison-v2

2017-03-07T18:28:31+00:00

The cache policy interfaces have been updated to work well with the new
bio-prison v2 interface's ability to queue work immediately (promotion,
demotion, etc) -- overriding benefit being reduced latency on processing
IO through the cache.  Previously such work would be left for the DM
cache core to queue on various lists and then process in batches later
-- this caused a serious delay in latency for IO driven by the cache.

The background tracker code was factored out so that all cache policies
can make use of it.

Also, the "cleaner" policy has been removed and is now a variant of the
smq policy that simply disallows migrations.

Signed-off-by: Joe Thornber 
Signed-off-by: Mike Snitzer