| /linux-6.1.9/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 | dm-log.rst | 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 | 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 | 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 \
|
| D | log-writes.rst | 85 mkfs.btrfs -f /dev/mapper/log
109 mkfs.btrfs -f /dev/mapper/log
112 mount /dev/mapper/log /mnt/btrfs-test
129 mkfs.btrfs -f /dev/mapper/log
132 mount /dev/mapper/log /mnt/btrfs-test
|
| D | zero.rst | 32 echo "0 $TEN_TERABYTES snapshot /dev/mapper/zero1 /dev/sdb1 p 128" | \
35 This will create a 10TB sparse device called /dev/mapper/sparse1 that has
|
| D | switch.rst | 5 The device-mapper switch target creates a device that supports an
42 A device-mapper table already lets you map different regions of a
48 Using this device-mapper switch target we can now build a two-layer
|
| D | persistent-data.rst | 8 The more-sophisticated device-mapper targets require complex metadata
21 framework for people who want to store metadata in device-mapper
|
| D | dm-init.rst | 5 It is possible to configure a device-mapper device to act as the root device for
77 this target to /dev/mapper/lroot (depending on the rules). No uuid was assigned.
|
| /linux-6.1.9/kernel/trace/ |
| D | trace_functions.c | 448 struct ftrace_func_mapper *mapper = data; in update_traceon_count() local
481 count = (long *)ftrace_func_mapper_find_ip(mapper, ip); in update_traceon_count()
586 struct ftrace_func_mapper *mapper = data; in ftrace_stacktrace_count() local
595 if (!mapper) { in ftrace_stacktrace_count()
600 count = (long *)ftrace_func_mapper_find_ip(mapper, ip); in ftrace_stacktrace_count()
626 struct ftrace_func_mapper *mapper = data; in update_count() local
629 if (mapper) in update_count()
630 count = (long *)ftrace_func_mapper_find_ip(mapper, ip); in update_count()
665 struct ftrace_func_mapper *mapper = data; in ftrace_probe_print() local
670 if (mapper) in ftrace_probe_print()
[all …]
|
| D | trace_events.c | 3177 struct ftrace_func_mapper *mapper = data; in event_enable_probe() local
3181 pdata = ftrace_func_mapper_find_ip(mapper, ip); in event_enable_probe()
3194 struct ftrace_func_mapper *mapper = data; in event_enable_count_probe() local
3198 pdata = ftrace_func_mapper_find_ip(mapper, ip); in event_enable_count_probe()
3221 struct ftrace_func_mapper *mapper = data; in event_enable_print() local
3225 pdata = ftrace_func_mapper_find_ip(mapper, ip); in event_enable_print()
3251 struct ftrace_func_mapper *mapper = *data; in event_enable_init() local
3255 if (!mapper) { in event_enable_init()
3256 mapper = allocate_ftrace_func_mapper(); in event_enable_init()
3257 if (!mapper) in event_enable_init()
[all …]
|
| /linux-6.1.9/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.
|
| D | sysfs-bus-iio-light-lm3533-als | 52 These values correspond to the ALS-mapper target registers for
53 ALS-mapper Y + 1.
|
| /linux-6.1.9/Documentation/power/ |
| D | swsusp-dmcrypt.rst | 36 brw------- 1 root root 254, 0 Jul 28 13:37 /dev/mapper/swap0
38 Now set up your kernel to use /dev/mapper/swap0 as the default
41 CONFIG_PM_STD_PARTITION="/dev/mapper/swap0"
104 mkswap /dev/mapper/swap0 > /dev/null 2>&1
128 then attempts to resume from the first device mapper device.
|
| /linux-6.1.9/drivers/gpu/drm/bridge/imx/ |
| D | Kconfig | 10 Freescale i.MX8qm processor. Official name of LDB is pixel mapper.
19 Freescale i.MX8qxp processor. Official name of LDB is pixel mapper.
|
| /linux-6.1.9/drivers/md/ |
| D | Kconfig | 204 tristate "Device mapper support"
210 Device-mapper is a low level volume manager. It works by allowing
223 bool "Device mapper debugging support"
226 Enable this for messages that may help debug device-mapper problems.
260 Some bio locking schemes used by other device-mapper targets
281 This device-mapper target allows you to create a device that
504 See Documentation/admin-guide/device-mapper/dm-init.rst for dm-mod.create="..."
528 This device-mapper target creates a read-only device that
580 This device-mapper target creates a device that supports an arbitrary
594 This device-mapper target takes two devices, one device to use
[all …]
|
| /linux-6.1.9/drivers/md/persistent-data/ |
| D | Kconfig | 9 device-mapper targets such as the thin provisioning target.
|
| /linux-6.1.9/drivers/usb/typec/ |
| D | Makefile | 4 typec-$(CONFIG_ACPI) += port-mapper.o
|
| /linux-6.1.9/net/ceph/ |
| D | Makefile | 10 osd_client.o osdmap.o crush/crush.o crush/mapper.o crush/hash.o \
|
| /linux-6.1.9/Documentation/devicetree/bindings/display/bridge/ |
| D | fsl,imx8qxp-ldb.yaml | 33 A side note is that i.MX8qm/qxp LDB is officially called pixel mapper in
34 the SoC reference manuals. The pixel mapper uses logic of LDBs embedded in
|
| /linux-6.1.9/Documentation/admin-guide/nfs/ |
| D | nfs-idmapper.rst | 5 Id mapper is used by NFS to translate user and group ids into names, and to
39 id mapper uses for key descriptions::
|
| /linux-6.1.9/Documentation/translations/zh_CN/admin-guide/ |
| D | index.rst | 90 * device-mapper/index
|