projects / linux-dmdedup.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: d379c28) | patch
dm-dedup: main data structures
authorVasily Tarasov <tarasov@vasily.name>
Thu, 28 Aug 2014 21:56:35 +0000 (17:56 -0400)
committerMike Snitzer <snitzer@redhat.com>
Mon, 22 Sep 2014 15:04:58 +0000 (11:04 -0400)
commitd627aa796a8bc5113aeefc85d5e1845ded825b65
treea16d99c61435b3a36cd51e8b7e34b4b7f362e508tree | snapshot
parentd379c2886c48b32d5f4cf70a27ba2409e127b6f7commit | diff
dm-dedup: main data structures

We maintain one dedup_config structure for every dm-dedup target
instance. Every target instance has a metadata backend associated with
it. Metadata backends should implement operations defined in the
metadata_ops structure. Every backend should support two key-value
stores: (1) sparse store, where the hash-to-pbn mapping (the hash index)
is stored; and (2) linear store, where the lbn-to-pbn mapping is stored.

Signed-off-by: Vasily Tarasov <tarasov@vasily.name>
drivers/md/dm-dedup-backend.h [new file with mode: 0644] blob
drivers/md/dm-dedup-kvstore.h [new file with mode: 0644] blob
drivers/md/dm-dedup-target.h [new file with mode: 0644] blob
linux-dmdedup