Lines Matching +full:multi +full:- +full:block

8 The more-sophisticated device-mapper targets require complex metadata
12 - Mikulas Patocka's multisnap implementation
13 - Heinz Mauelshagen's thin provisioning target
14 - Another btree-based caching target posted to dm-devel
15 - Another multi-snapshot target based on a design of Daniel Phillips
20 The persistent-data library is an attempt to provide a re-usable
21 framework for people who want to store metadata in device-mapper
22 targets.  It's currently used by the thin-provisioning target and an
29 under drivers/md/persistent-data.
31 The block manager
32 -----------------
34 dm-block-manager.[hc]
36 This provides access to the data on disk in fixed sized-blocks.  There
40 Clients of persistent-data are unlikely to use this directly.
43 -----------------------
45 dm-transaction-manager.[hc]
47 This restricts access to blocks and enforces copy-on-write semantics.
48 The only way you can get hold of a writable block through the
49 transaction manager is by shadowing an existing block (ie. doing
50 copy-on-write) or allocating a fresh one.  Shadowing is elided within
56 --------------
58 dm-space-map.h
59 dm-space-map-metadata.[hc]
60 dm-space-map-disk.[hc]
62 On-disk data structures that keep track of reference counts of blocks.
65 device (eg. thinly-provisioned data blocks); and one for managing
70 -------------------
72 dm-btree.[hc]
73 dm-btree-remove.c
74 dm-btree-spine.c
75 dm-btree-internal.h
79 array-like interface would see a lot of use.
83 thin-provisioning target uses a btree with two levels of nesting.
85 virtual block to a physical block.