Home
last modified time | relevance | path

Searched full:dm (Results 1 – 25 of 75) sorted by relevance

123

/Documentation/admin-guide/device-mapper/
Dindex.rst11 dm-clone
12 dm-crypt
13 dm-dust
14 dm-ebs
15 dm-flakey
16 dm-ima
17 dm-init
18 dm-integrity
19 dm-io
20 dm-log
[all …]
Ddm-init.rst12 "dm-mod.create=" through the kernel boot command line argument.
23 …dm-mod.create=<name>,<uuid>,<minor>,<flags>,<table>[,<table>+][;<name>,<uuid>,<minor>,<flags>,<tab…
34 The dm line should be equivalent to the one used by the dmsetup tool with the
41 activation of certain DM targets without first using userspace tools to check
59 `thin` constrained, requires dm target message from userspace
60 `thin-pool` constrained, requires dm target message from userspace
73 dm-mod.create="lroot,,,rw, 0 4096 linear 98:16 0, 4096 4096 linear 98:32 0" root=/dev/dm-0
75 This will boot to a rw dm-linear target of 8192 sectors split across two block
79 An example of multiple device-mappers, with the dm-mod.create="..." contents
82 dm-linear,,1,rw,
[all …]
Ddm-clone.rst4 dm-clone
10 dm-clone is a device mapper target which produces a one-to-one copy of an
15 The main use case of dm-clone is to clone a potentially remote, high-latency,
26 When the cloning completes, the dm-clone table can be removed altogether and be
29 The dm-clone target reuses the metadata library used by the thin-provisioning
68 dm-clone divides the source and destination devices in fixed sized regions.
72 The region size is configurable when you first create the dm-clone device. The
92 dm-clone interprets a discard request to a range that hasn't been hydrated yet
97 If the destination device supports discards, then by default dm-clone will pass
103 dm-clone copies continuously from the source to the destination device, until
[all …]
Dpersistent-data.rst14 - Another btree-based caching target posted to dm-devel
34 dm-block-manager.[hc]
45 dm-transaction-manager.[hc]
58 dm-space-map.h
59 dm-space-map-metadata.[hc]
60 dm-space-map-disk.[hc]
72 dm-btree.[hc]
73 dm-btree-remove.c
74 dm-btree-spine.c
75 dm-btree-internal.h
Ddm-integrity.rst2 dm-integrity
5 The dm-integrity target emulates a block device that has additional
12 To guarantee write atomicity, the dm-integrity target uses journal, it
16 The dm-integrity target can be used with the dm-crypt target - in this
17 situation the dm-crypt target creates the integrity data and passes them
18 to the dm-integrity target via bio_integrity_payload attached to the bio.
19 In this mode, the dm-crypt and dm-integrity targets provide authenticated
23 The dm-integrity target can also be used as a standalone target, in this
25 mode, the dm-integrity target can be used to detect silent data
28 There's an alternate mode of operation where dm-integrity uses a bitmap
[all …]
Dzero.rst2 dm-zero
9 Dm-zero has no target-specific parameters.
11 One very interesting use of dm-zero is for creating "sparse" devices in
12 conjunction with dm-snapshot. A sparse device reports a device-size larger
20 To create a sparse device, start by creating a dm-zero device that's the
Ddm-io.rst2 dm-io
5 Dm-io provides synchronous and asynchronous I/O services. There are three
19 Dm-io can read from one io_region or write to one or more io_regions. Writes
65 In the case of an write-I/O to multiple regions, this bitset allows dm-io to
68 Before using any of the dm-io services, the user should call dm_io_get()
70 Dm-io will attempt to resize its mempool to make sure enough pages are
73 When the user is finished using the dm-io services, they should call
Ddm-queue-length.rst2 dm-queue-length
5 dm-queue-length is a path selector module for device-mapper targets,
30 dm-queue-length increments/decrements 'in-flight' when an I/O is
32 dm-queue-length selects a path with the minimum 'in-flight'.
Ddm-log.rst16 dm_dirty_log_type in include/linux/dm-dirty-log.h). Various different
23 disk drivers/md/dm-log.c
24 core drivers/md/dm-log.c
25 userspace drivers/md/dm-log-userspace* include/linux/dm-log-userspace.h
48 located in include/linux/dm-log-userspace.h. Due to the frequency,
Ddm-zoned.rst2 dm-zoned
5 The dm-zoned device mapper target exposes a zoned block device (ZBC and
23 The dm-zoned implementation is simple and minimizes system overhead (CPU
25 host-managed disk with 256 MB zones, dm-zoned memory usage per disk
29 dm-zoned target devices are formatted and checked using the dmzadm
32 https://github.com/hgst/dm-zoned-tools
37 dm-zoned implements an on-disk buffering scheme to handle non-sequential
58 dm-zoned exposes a logical device with a sector size of 4096 bytes,
173 dmsetup status /dev/dm-X
191 dmsetup message /dev/dm-X 0 reclaim
Ddm-crypt.rst2 dm-crypt
117 Set dm-crypt workqueues and the writer thread to high priority. This
118 improves throughput and latency of dm-crypt while degrading general
130 Bypass dm-crypt internal workqueue and process read requests synchronously.
133 Bypass dm-crypt internal workqueue and process write requests synchronously.
140 by underlying dm-integrity target.
171 is received, dm-crypt will split the request. The splitting improves
178 is received, dm-crypt will split the request. The splitting improves
187 encryption with dm-crypt using the 'cryptsetup' utility, see
Dstatistics.rst2 DM statistics
6 regions of a DM device. If no regions are defined no statistics are
7 collected so there isn't any performance impact. Only bio-based DM
20 the @stats_print message to the appropriate DM device via dmsetup.
30 request and process statistics for the same DM device without stepping
33 The creation of DM statistics will allocate memory via kmalloc or
35 memory may be allocated by DM statistics. The admin can see how much
205 Subdivide the DM device 'vol' into 100 pieces and start collecting
Dvdo.rst3 dm-vdo
6 The dm-vdo (virtual data optimizer) device mapper target provides
20 https://github.com/dm-vdo/vdo/
35 rarely needed except by dm-vdo developers.
46 https://github.com/dm-vdo/vdoestimator/
194 physical space, storing to /dev/dm-1 which has more than 1 GB of space.
199 "0 2097152 vdo V4 /dev/dm-1 262144 4096 32768 16380"
206 "0 8388608 vdo V4 /dev/dm-1 262144 4096 32768 16380"
214 "0 8388608 vdo V4 /dev/dm-1 524288 4096 32768 16380"
222 "0 10485760 vdo V4 /dev/dm-1 786432 4096 32768 16380 maxDiscard 8"
[all …]
Dera.rst2 dm-era
8 dm-era is a target that behaves similar to the linear target. In
33 None of the dm messages take any arguments.
86 - Cache enters passthrough mode (see: dm-cache's docs in cache.txt)
107 block is performed. As such dm-era should not be effected by a hard
Ddm-uevent.rst80 UEVENT[1192521009.711215] change@/block/dm-3
82 DEVPATH=/block/dm-3
97 UEVENT[1192521132.989927] change@/block/dm-3
99 DEVPATH=/block/dm-3
Ddm-service-time.rst2 dm-service-time
5 dm-service-time is a path selector module for device-mapper targets,
49 dm-service-time adds the I/O size to 'in-flight-size' when the I/O is
51 Basically, dm-service-time selects a path having minimum service time
Dswitch.rst2 dm-switch
13 dm-stripe.
54 The lower tier consists of a single dm multipath device for each member.
61 The upper tier consists of a single dm-switch device. This device uses
65 large for us). This is a much denser representation than the dm table
Dkcopyd.rst7 notification. It is used by dm-snapshot and dm-mirror.
Dverity.rst2 dm-verity
40 dm-verity device.
122 rather than every time. This reduces the overhead of dm-verity so that it
158 dm-verity is meant to be set up as part of a verified boot path. This
162 When a dm-verity device is configured, it is expected that the caller
Ddm-flakey.rst2 dm-flakey
13 Also, consider using this in combination with the dm-delay target too,
Ddm-ima.rst2 dm-ima
76 | The DM target data measured by IMA subsystem can alternatively
115 device_name := "name=" <dm-device-name>
116 device_uuid := "uuid=" <dm-device-uuid>
121 dm-device-name := Name of the device. If it contains special characters like '\', ',', ';',
123 dm-device-uuid := UUID of the device. If it contains special characters like '\', ',', ';',
128 which is being loaded into the DM device's inactive table slot.
293 new_device_name := "new_name=" <dm-device-name>
294 dm-device-name := Same as <dm-device-name> described in 'Table load' section above
295 new_device_uuid := "new_uuid=" <dm-device-uuid>
[all …]
/Documentation/ABI/testing/
Dsysfs-block-dm1 What: /sys/block/dm-<num>/dm/name
4 Contact: dm-devel@redhat.com
9 What: /sys/block/dm-<num>/dm/uuid
12 Contact: dm-devel@redhat.com
14 Read-only string containing DM-UUID or empty string
15 if DM-UUID is not set.
18 What: /sys/block/dm-<num>/dm/suspended
21 Contact: dm-devel@redhat.com
27 What: /sys/block/dm-<num>/dm/rq_based_seq_io_merge_deadline
30 Contact: dm-devel@redhat.com
[all …]
/Documentation/power/
Dswsusp-dmcrypt.rst2 How to use dm-crypt and swsusp together
10 You know how dm-crypt works. If not, visit the following web page:
11 http://www.saout.de/misc/dm-crypt/
26 up dm-crypt and then asks swsusp to resume from the encrypted
29 The most important thing is that you set up dm-crypt in such
53 you create an initrd that reads the required dm-crypt setup
/Documentation/device-mapper/
Ddm-bow.txt9 dm_bow has three states, set by writing ‘1’ or ‘2’ to /sys/block/dm-?/bow/state.
34 dm-bow takes one command line parameter, the name of the underlying device.
36 dm-bow will typically be used in the following way. dm-bow will be loaded with a
41 unmounting the file system, removing the dm-bow device and running the command
/Documentation/filesystems/
Dubifs-authentication.rst28 Other full disk encryption systems like dm-crypt cover all filesystem metadata,
31 time. For dm-crypt and other filesystems that build upon the Linux block IO
32 layer, the dm-integrity or dm-verity subsystems [DM-INTEGRITY, DM-VERITY]
34 These can also be combined with dm-crypt [CRYPTSETUP2].
438 [CRYPTSETUP2] https://www.saout.de/pipermail/dm-crypt/2017-November/005745.html
442 [DM-INTEGRITY] https://www.kernel.org/doc/Documentation/device-mapper/dm-integrity.rst
444 [DM-VERITY] https://www.kernel.org/doc/Documentation/device-mapper/verity.rst

123