| /kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/ |
| D | dm-uevent.rst | 2 device-mapper uevent
5 The device-mapper uevent code adds the capability to device-mapper to create
6 and send kobject uevents (uevents). Previously device-mapper events were only
9 the event avoiding the need to query the state of the device-mapper device after
12 There are two functions currently for device-mapper events. The first function
28 :Value: Name of device-mapper target that generated the event.
35 :Value: Device-mapper specific action that caused the uevent action.
43 :Description: A sequence number for this specific device-mapper device.
65 :Description: Name of the device-mapper device.
72 :Description: UUID of the device-mapper device.
|
| D | unstriped.rst | 2 Device-mapper "unstriped" target
8 The device-mapper "unstriped" target provides a transparent mechanism to
9 unstripe a device-mapper "striped" target to access the underlying disks
63 echo "0 1 unstriped ${NUM} ${CHUNK} ${i} /dev/mapper/raid0 0" | dmsetup create set-${i}
67 dd if=/dev/urandom of=/dev/mapper/set-${i} bs=${BS} count=${COUNT} oflag=direct
68 diff /dev/mapper/set-${i} member-${i}
107 to get a 92% reduction in read latency using this device mapper target.
124 /dev/mapper/nvmset0
125 /dev/mapper/nvmset1
132 dmsetup create raid_disk0 --table '0 512 unstriped 4 256 0 /dev/mapper/striped 0'
[all …]
|
| D | dm-dust.rst | 78 $ sudo dd if=/dev/mapper/dust1 of=/dev/null bs=512 count=128 iflag=direct
82 $ sudo dd if=/dev/zero of=/dev/mapper/dust1 bs=512 count=128 oflag=direct
94 kernel: device-mapper: dust: badblock added at block 60
97 kernel: device-mapper: dust: badblock added at block 67
100 kernel: device-mapper: dust: badblock added at block 72
114 kernel: device-mapper: dust: enabling read failures on bad sectors
122 $ sudo dd if=/dev/mapper/dust1 of=/dev/null bs=512 count=1 skip=67 iflag=direct
123 dd: error reading '/dev/mapper/dust1': Input/output error
131 $ sudo dd if=/dev/zero of=/dev/mapper/dust1 bs=512 count=128 oflag=direct
135 kernel: device-mapper: dust: block 60 removed from badblocklist by write
[all …]
|
| D | snapshot.rst | 2 Device-mapper snapshot support
5 Device-mapper allows you, without massive data copying:
117 # ls -lL /dev/mapper/volumeGroup-*
118 brw------- 1 root root 254, 11 29 ago 18:15 /dev/mapper/volumeGroup-base-real
119 brw------- 1 root root 254, 12 29 ago 18:15 /dev/mapper/volumeGroup-snap-cow
120 brw------- 1 root root 254, 13 29 ago 18:15 /dev/mapper/volumeGroup-snap
121 brw------- 1 root root 254, 10 29 ago 18:14 /dev/mapper/volumeGroup-base
146 # ls -lL /dev/mapper/volumeGroup-*
147 brw------- 1 root root 254, 11 29 ago 18:15 /dev/mapper/volumeGroup-base-real
148 brw------- 1 root root 254, 12 29 ago 18:16 /dev/mapper/volumeGroup-base-cow
[all …]
|
| D | thin-provisioning.rst | 8 This document describes a collection of device-mapper targets that
46 a Red Hat distribution it is named 'device-mapper-persistent-data').
52 They use the dmsetup program to control the device-mapper driver
65 - Device-mapper 'messages' from userspace which control the creation of new
163 active pool device, /dev/mapper/pool in this example::
165 dmsetup message /dev/mapper/pool 0 "create_thin 0"
175 dmsetup create thin --table "0 2097152 thin /dev/mapper/pool 0"
192 dmsetup suspend /dev/mapper/thin
193 dmsetup message /dev/mapper/pool 0 "create_snap 1 0"
194 dmsetup resume /dev/mapper/thin
[all …]
|
| D | dm-log.rst | 2 Device-Mapper Logging
4 The device-mapper logging code is used by some of the device-mapper
14 There is a generic logging interface that the device-mapper RAID
55 provide a cluster-coherent log for shared-storage. Device-mapper mirroring
|
| D | cache.rst | 8 dm-cache is a device mapper target written by Joe Thornber, Heinz
15 This device-mapper solution allows us to insert this caching at
159 need a generic way of getting and setting these. Device-mapper
296 need a generic way of getting and setting these. Device-mapper
329 https://github.com/jthornber/device-mapper-test-suite
333 dmsetup create my_cache --table '0 41943040 cache /dev/mapper/metadata \
334 /dev/mapper/ssd /dev/mapper/origin 512 1 writeback default 0'
335 dmsetup create my_cache --table '0 41943040 cache /dev/mapper/metadata \
336 /dev/mapper/ssd /dev/mapper/origin 1024 1 writeback \
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/device-mapper/ |
| D | dm-uevent.rst | 2 device-mapper uevent
5 The device-mapper uevent code adds the capability to device-mapper to create
6 and send kobject uevents (uevents). Previously device-mapper events were only
9 the event avoiding the need to query the state of the device-mapper device after
12 There are two functions currently for device-mapper events. The first function
28 :Value: Name of device-mapper target that generated the event.
35 :Value: Device-mapper specific action that caused the uevent action.
43 :Description: A sequence number for this specific device-mapper device.
65 :Description: Name of the device-mapper device.
72 :Description: UUID of the device-mapper device.
|
| D | unstriped.rst | 2 Device-mapper "unstriped" target
8 The device-mapper "unstriped" target provides a transparent mechanism to
9 unstripe a device-mapper "striped" target to access the underlying disks
63 echo "0 1 unstriped ${NUM} ${CHUNK} ${i} /dev/mapper/raid0 0" | dmsetup create set-${i}
67 dd if=/dev/urandom of=/dev/mapper/set-${i} bs=${BS} count=${COUNT} oflag=direct
68 diff /dev/mapper/set-${i} member-${i}
107 to get a 92% reduction in read latency using this device mapper target.
124 /dev/mapper/nvmset0
125 /dev/mapper/nvmset1
132 dmsetup create raid_disk0 --table '0 512 unstriped 4 256 0 /dev/mapper/striped 0'
[all …]
|
| D | dm-dust.rst | 78 $ sudo dd if=/dev/mapper/dust1 of=/dev/null bs=512 count=128 iflag=direct
82 $ sudo dd if=/dev/zero of=/dev/mapper/dust1 bs=512 count=128 oflag=direct
94 kernel: device-mapper: dust: badblock added at block 60
97 kernel: device-mapper: dust: badblock added at block 67
100 kernel: device-mapper: dust: badblock added at block 72
114 kernel: device-mapper: dust: enabling read failures on bad sectors
122 $ sudo dd if=/dev/mapper/dust1 of=/dev/null bs=512 count=1 skip=67 iflag=direct
123 dd: error reading '/dev/mapper/dust1': Input/output error
131 $ sudo dd if=/dev/zero of=/dev/mapper/dust1 bs=512 count=128 oflag=direct
135 kernel: device-mapper: dust: block 60 removed from badblocklist by write
[all …]
|
| D | snapshot.rst | 2 Device-mapper snapshot support
5 Device-mapper allows you, without massive data copying:
117 # ls -lL /dev/mapper/volumeGroup-*
118 brw------- 1 root root 254, 11 29 ago 18:15 /dev/mapper/volumeGroup-base-real
119 brw------- 1 root root 254, 12 29 ago 18:15 /dev/mapper/volumeGroup-snap-cow
120 brw------- 1 root root 254, 13 29 ago 18:15 /dev/mapper/volumeGroup-snap
121 brw------- 1 root root 254, 10 29 ago 18:14 /dev/mapper/volumeGroup-base
146 # ls -lL /dev/mapper/volumeGroup-*
147 brw------- 1 root root 254, 11 29 ago 18:15 /dev/mapper/volumeGroup-base-real
148 brw------- 1 root root 254, 12 29 ago 18:16 /dev/mapper/volumeGroup-base-cow
[all …]
|
| D | thin-provisioning.rst | 8 This document describes a collection of device-mapper targets that
46 a Red Hat distribution it is named 'device-mapper-persistent-data').
52 They use the dmsetup program to control the device-mapper driver
65 - Device-mapper 'messages' from userspace which control the creation of new
163 active pool device, /dev/mapper/pool in this example::
165 dmsetup message /dev/mapper/pool 0 "create_thin 0"
175 dmsetup create thin --table "0 2097152 thin /dev/mapper/pool 0"
192 dmsetup suspend /dev/mapper/thin
193 dmsetup message /dev/mapper/pool 0 "create_snap 1 0"
194 dmsetup resume /dev/mapper/thin
[all …]
|
| D | dm-log.rst | 2 Device-Mapper Logging
4 The device-mapper logging code is used by some of the device-mapper
14 There is a generic logging interface that the device-mapper RAID
55 provide a cluster-coherent log for shared-storage. Device-mapper mirroring
|
| D | cache.rst | 8 dm-cache is a device mapper target written by Joe Thornber, Heinz
15 This device-mapper solution allows us to insert this caching at
159 need a generic way of getting and setting these. Device-mapper
296 need a generic way of getting and setting these. Device-mapper
329 https://github.com/jthornber/device-mapper-test-suite
333 dmsetup create my_cache --table '0 41943040 cache /dev/mapper/metadata \
334 /dev/mapper/ssd /dev/mapper/origin 512 1 writeback default 0'
335 dmsetup create my_cache --table '0 41943040 cache /dev/mapper/metadata \
336 /dev/mapper/ssd /dev/mapper/origin 1024 1 writeback \
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-block-dm | 5 Description: Device-mapper device name.
7 Users: util-linux, device-mapper udev rules
13 Description: Device-mapper device UUID.
16 Users: util-linux, device-mapper udev rules
22 Description: Device-mapper device suspend state.
25 Users: util-linux, device-mapper udev rules
45 Description: Request-based Device-mapper blk-mq I/O path mode.
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-block-dm | 5 Description: Device-mapper device name.
7 Users: util-linux, device-mapper udev rules
13 Description: Device-mapper device UUID.
16 Users: util-linux, device-mapper udev rules
22 Description: Device-mapper device suspend state.
25 Users: util-linux, device-mapper udev rules
45 Description: Request-based Device-mapper blk-mq I/O path mode.
|
| /kernel/linux/linux-5.10/drivers/infiniband/core/ |
| D | iwpm_msg.c | 42 * iwpm_valid_pid - Check if the userspace iwarp port mapper pid is valid
53 * to get the iwarp port mapper pid
54 * @pm_msg: Contains driver info to send to the userspace port mapper
73 err_str = "Invalid port mapper client"; in iwpm_register_pid()
135 * the userspace port mapper
145 * the port mapper response (mapped address info)
157 err_str = "Invalid port mapper client"; in iwpm_add_mapping()
163 err_str = "Unregistered port mapper client"; in iwpm_add_mapping()
223 * iwpm_add_and_query_mapping - Process the port mapper response to
244 err_str = "Invalid port mapper client"; in iwpm_add_and_query_mapping()
[all …]
|
| D | iwpm_util.h | 137 * message to send to the port mapper
151 * iwpm_valid_client - Check if the port mapper client is valid
155 * the port mapper
160 * iwpm_set_valid - Set the port mapper client to valid or not
195 * a client to the user space port mapper
197 * @iwpm_pid: The pid of the user space port mapper
277 * @iwpm_pid: The pid of the user space port mapper
|
| /kernel/linux/linux-5.10/kernel/trace/ |
| D | trace_functions.c | 292 struct ftrace_func_mapper *mapper = data; in update_traceon_count() local
325 count = (long *)ftrace_func_mapper_find_ip(mapper, ip); in update_traceon_count()
432 struct ftrace_func_mapper *mapper = data; in ftrace_stacktrace_count() local
441 if (!mapper) { in ftrace_stacktrace_count()
446 count = (long *)ftrace_func_mapper_find_ip(mapper, ip); in ftrace_stacktrace_count()
472 struct ftrace_func_mapper *mapper = data; in update_count() local
475 if (mapper) in update_count()
476 count = (long *)ftrace_func_mapper_find_ip(mapper, ip); in update_count()
511 struct ftrace_func_mapper *mapper = data; in ftrace_probe_print() local
516 if (mapper) in ftrace_probe_print()
[all …]
|
| /kernel/linux/linux-6.6/drivers/infiniband/core/ |
| D | iwpm_msg.c | 42 * iwpm_valid_pid - Check if the userspace iwarp port mapper pid is valid
53 * to get the iwarp port mapper pid
54 * @pm_msg: Contains driver info to send to the userspace port mapper
131 * the userspace port mapper
141 * the port mapper response (mapped address info)
155 err_str = "Unregistered port mapper client"; in iwpm_add_mapping()
215 * iwpm_add_and_query_mapping - Process the port mapper response to
238 err_str = "Unregistered port mapper client"; in iwpm_add_and_query_mapping()
305 * to the userspace port mapper
325 err_str = "Unregistered port mapper client"; in iwpm_remove_mapping()
[all …]
|
| /kernel/linux/linux-6.6/kernel/trace/ |
| D | trace_functions.c | 446 struct ftrace_func_mapper *mapper = data; in update_traceon_count() local
479 count = (long *)ftrace_func_mapper_find_ip(mapper, ip); in update_traceon_count()
580 struct ftrace_func_mapper *mapper = data; in ftrace_stacktrace_count() local
589 if (!mapper) { in ftrace_stacktrace_count()
594 count = (long *)ftrace_func_mapper_find_ip(mapper, ip); in ftrace_stacktrace_count()
620 struct ftrace_func_mapper *mapper = data; in update_count() local
623 if (mapper) in update_count()
624 count = (long *)ftrace_func_mapper_find_ip(mapper, ip); in update_count()
659 struct ftrace_func_mapper *mapper = data; in ftrace_probe_print() local
664 if (mapper) in ftrace_probe_print()
[all …]
|
| /kernel/linux/linux-5.10/sound/pci/ctxfi/ |
| D | ctimap.h | 8 * This file contains the definition of generic input mapper operations
9 * for input mapper management.
23 unsigned short addr; /* the input mapper ram id */
24 unsigned short next; /* the next input mapper ram id */
|
| /kernel/linux/linux-6.6/sound/pci/ctxfi/ |
| D | ctimap.h | 8 * This file contains the definition of generic input mapper operations
9 * for input mapper management.
23 unsigned short addr; /* the input mapper ram id */
24 unsigned short next; /* the next input mapper ram id */
|
| /kernel/linux/linux-6.6/drivers/md/ |
| D | Kconfig | 218 tristate "Device mapper support"
224 Device-mapper is a low level volume manager. It works by allowing
237 bool "Device mapper debugging support"
240 Enable this for messages that may help debug device-mapper problems.
274 Some bio locking schemes used by other device-mapper targets
295 This device-mapper target allows you to create a device that
518 See Documentation/admin-guide/device-mapper/dm-init.rst for dm-mod.create="..."
542 This device-mapper target creates a read-only device that
594 This device-mapper target creates a device that supports an arbitrary
608 This device-mapper target takes two devices, one device to use
[all …]
|
| /kernel/linux/linux-5.10/drivers/md/ |
| D | Kconfig | 203 tristate "Device mapper support"
207 Device-mapper is a low level volume manager. It works by allowing
220 bool "Device mapper debugging support"
223 Enable this for messages that may help debug device-mapper problems.
257 Some bio locking schemes used by other device-mapper targets
277 This device-mapper target allows you to create a device that
491 See Documentation/admin-guide/device-mapper/dm-init.rst for dm-mod.create="..."
515 This device-mapper target creates a read-only device that
556 This device-mapper target creates a device that supports an arbitrary
570 This device-mapper target takes two devices, one device to use
[all …]
|