Searched refs:mapper (Results 1 – 27 of 27) sorted by relevance
| /linux-4.1.27/Documentation/device-mapper/ |
| D | dm-uevent.txt | 1 The device-mapper uevent code adds the capability to device-mapper to create
2 and send kobject uevents (uevents). Previously device-mapper events were only
5 the event avoiding the need to query the state of the device-mapper device after
8 There are two functions currently for device-mapper events. The first function
23 Value: Name of device-mapper target that generated the event.
29 Value: Device-mapper specific action that caused the uevent action.
36 Description: A sequence number for this specific device-mapper device.
55 Description: Name of the device-mapper device.
61 Description: UUID of the device-mapper device.
|
| D | snapshot.txt | 1 Device-mapper snapshot support
4 Device-mapper allows you, without massive data copying:
92 # ls -lL /dev/mapper/volumeGroup-*
93 brw------- 1 root root 254, 11 29 ago 18:15 /dev/mapper/volumeGroup-base-real
94 brw------- 1 root root 254, 12 29 ago 18:15 /dev/mapper/volumeGroup-snap-cow
95 brw------- 1 root root 254, 13 29 ago 18:15 /dev/mapper/volumeGroup-snap
96 brw------- 1 root root 254, 10 29 ago 18:14 /dev/mapper/volumeGroup-base
121 # ls -lL /dev/mapper/volumeGroup-*
122 brw------- 1 root root 254, 11 29 ago 18:15 /dev/mapper/volumeGroup-base-real
123 brw------- 1 root root 254, 12 29 ago 18:16 /dev/mapper/volumeGroup-base-cow
[all …]
|
| D | dm-log.txt | 3 The device-mapper logging code is used by some of the device-mapper
13 There is a generic logging interface that the device-mapper RAID
52 provide a cluster-coherent log for shared-storage. Device-mapper mirroring
|
| D | thin-provisioning.txt | 4 This document describes a collection of device-mapper targets that
47 They use the dmsetup program to control the device-mapper driver
60 - Device-mapper 'messages' from userspace which control the creation of new
154 active pool device, /dev/mapper/pool in this example.
156 dmsetup message /dev/mapper/pool 0 "create_thin 0"
166 dmsetup create thin --table "0 2097152 thin /dev/mapper/pool 0"
181 dmsetup suspend /dev/mapper/thin
182 dmsetup message /dev/mapper/pool 0 "create_snap 1 0"
183 dmsetup resume /dev/mapper/thin
196 device-mapper snapshots.)
[all …]
|
| D | cache.txt | 4 dm-cache is a device mapper target written by Joe Thornber, Heinz
11 This device-mapper solution allows us to insert this caching at
157 need a generic way of getting and setting these. Device-mapper
261 need a generic way of getting and setting these. Device-mapper
292 https://github.com/jthornber/device-mapper-test-suite
294 dmsetup create my_cache --table '0 41943040 cache /dev/mapper/metadata \
295 /dev/mapper/ssd /dev/mapper/origin 512 1 writeback default 0'
296 dmsetup create my_cache --table '0 41943040 cache /dev/mapper/metadata \
297 /dev/mapper/ssd /dev/mapper/origin 1024 1 writeback \
|
| D | log-writes.txt | 80 mkfs.btrfs -f /dev/mapper/log
104 mkfs.btrfs -f /dev/mapper/log
107 mount /dev/mapper/log /mnt/btrfs-test
124 mkfs.btrfs -f /dev/mapper/log
127 mount /dev/mapper/log /mnt/btrfs-test
|
| D | zero.txt | 31 echo "0 $TEN_TERABYTES snapshot /dev/mapper/zero1 /dev/sdb1 p 128" | \
34 This will create a 10TB sparse device called /dev/mapper/sparse1 that has
|
| D | switch.txt | 4 The device-mapper switch target creates a device that supports an
41 A device-mapper table already lets you map different regions of a
47 Using this device-mapper switch target we can now build a two-layer
|
| D | persistent-data.txt | 4 The more-sophisticated device-mapper targets require complex metadata
17 framework for people who want to store metadata in device-mapper
|
| D | dm-queue-length.txt | 4 dm-queue-length is a path selector module for device-mapper targets,
|
| D | dm-raid.txt | 4 The device-mapper RAID (dm-raid) target provides a bridge from DM to MD.
5 It allows the MD RAID drivers to be accessed using a device-mapper
164 Line 1 is the standard output produced by device-mapper.
|
| D | dm-service-time.txt | 4 dm-service-time is a path selector module for device-mapper targets,
|
| /linux-4.1.27/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 | 60 These values correspond to the ALS-mapper target registers for
61 ALS-mapper Y + 1.
|
| /linux-4.1.27/Documentation/power/ |
| D | swsusp-dmcrypt.txt | 34 brw------- 1 root root 254, 0 Jul 28 13:37 /dev/mapper/swap0
36 Now set up your kernel to use /dev/mapper/swap0 as the default
39 CONFIG_PM_STD_PARTITION="/dev/mapper/swap0"
102 mkswap /dev/mapper/swap0 > /dev/null 2>&1
126 then attempts to resume from the first device mapper device.
|
| /linux-4.1.27/net/ceph/ |
| D | Makefile | 8 osd_client.o osdmap.o crush/crush.o crush/mapper.o crush/hash.o \
|
| /linux-4.1.27/drivers/md/persistent-data/ |
| D | Kconfig | 8 device-mapper targets such as the thin provisioning target.
|
| /linux-4.1.27/drivers/md/ |
| D | Kconfig | 200 tristate "Device mapper support"
203 Device-mapper is a low level volume manager. It works by allowing
227 bool "Device mapper debugging support"
230 Enable this for messages that may help debug device-mapper problems.
246 Some bio locking schemes used by other device-mapper targets
257 This device-mapper target allows you to create a device that
435 This device-mapper target creates a read-only device that
452 This device-mapper target creates a device that supports an arbitrary
466 This device-mapper target takes two devices, one device to use
|
| /linux-4.1.27/Documentation/filesystems/nfs/ |
| D | idmapper.txt | 5 Id mapper is used by NFS to translate user and group ids into names, and to
38 id mapper uses for key descriptions:
|
| /linux-4.1.27/drivers/staging/android/ion/ |
| D | ion_cma_heap.c | 138 static int ion_cma_mmap(struct ion_heap *mapper, struct ion_buffer *buffer, in ion_cma_mmap() argument
|
| D | ion_priv.h | 121 int (*map_user)(struct ion_heap *mapper, struct ion_buffer *buffer,
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | ntfs.txt | 362 If it all worked, you will now have the device /dev/device-mapper/myvolume1
366 $ mount -t ntfs -o ro /dev/device-mapper/myvolume1 /mnt/myvol1
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | blkio-controller.txt | 16 used on leaf nodes as well as higher level logical devices like device mapper.
|
| /linux-4.1.27/Documentation/ |
| D | 00-INDEX | 154 device-mapper/
|
| D | devices.txt | 453 236 = /dev/mapper/control Device-Mapper control device
|
| /linux-4.1.27/drivers/platform/x86/ |
| D | Kconfig | 569 Instrumentation) mapper device (PNP0C14) found on some systems.
|
| /linux-4.1.27/ |
| D | MAINTAINERS | 3152 T: git git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git
3155 F: Documentation/device-mapper/
3158 F: include/linux/device-mapper.h
|