dm zoned: separate random and cache zones

Browse source

Instead of lumping emulated zones together with random zones we
should be handling them as separate 'cache' zones. This improves
code readability and allows an easier implementation of different
cache policies.

Also add additional allocation flags, to separate the type (cache,
random, or sequential) from the purpose (eg reclaim).

Also switch the allocation policy to not use random zones as buffer
zones if cache zones are present. This avoids a performance drop when
all cache zones are used.

Signed-off-by: Hannes Reinecke <hare@suse.de>
Reviewed-by: Damien Le Moal <damien.lemoal@wdc.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>

...

This commit is contained in:

Hannes Reinecke 2020-05-19 10:14:20 +02:00 • committed by Mike Snitzer

parent 489dc0f06a

commit 34f5affd04

4 changed files with 159 additions and 67 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

123

drivers/md/dm-zoned-metadata.c

View file

76

drivers/md/dm-zoned-reclaim.c

View file

19

drivers/md/dm-zoned-target.c

View file

8

drivers/md/dm-zoned.h

View file