Home
last modified time | relevance | path

Searched refs:mapper (Results 1 – 25 of 36) sorted by relevance

12

/Linux-v4.19/drivers/gpu/drm/amd/amdgpu/
Damdgpu_queue_mgr.c28 static int amdgpu_queue_mapper_init(struct amdgpu_queue_mapper *mapper, in amdgpu_queue_mapper_init() argument
31 if (!mapper) in amdgpu_queue_mapper_init()
37 mapper->hw_ip = hw_ip; in amdgpu_queue_mapper_init()
38 mutex_init(&mapper->lock); in amdgpu_queue_mapper_init()
40 memset(mapper->queue_map, 0, sizeof(mapper->queue_map)); in amdgpu_queue_mapper_init()
45 static struct amdgpu_ring *amdgpu_get_cached_map(struct amdgpu_queue_mapper *mapper, in amdgpu_get_cached_map() argument
48 return mapper->queue_map[ring]; in amdgpu_get_cached_map()
51 static int amdgpu_update_cached_map(struct amdgpu_queue_mapper *mapper, in amdgpu_update_cached_map() argument
54 if (WARN_ON(mapper->queue_map[ring])) { in amdgpu_update_cached_map()
59 mapper->queue_map[ring] = pring; in amdgpu_update_cached_map()
[all …]
/Linux-v4.19/kernel/trace/
Dtrace_functions.c286 struct ftrace_func_mapper *mapper = data; in update_traceon_count() local
319 count = (long *)ftrace_func_mapper_find_ip(mapper, ip); in update_traceon_count()
426 struct ftrace_func_mapper *mapper = data; in ftrace_stacktrace_count() local
435 if (!mapper) { in ftrace_stacktrace_count()
440 count = (long *)ftrace_func_mapper_find_ip(mapper, ip); in ftrace_stacktrace_count()
466 struct ftrace_func_mapper *mapper = data; in update_count() local
469 if (mapper) in update_count()
470 count = (long *)ftrace_func_mapper_find_ip(mapper, ip); in update_count()
505 struct ftrace_func_mapper *mapper = data; in ftrace_probe_print() local
510 if (mapper) in ftrace_probe_print()
[all …]
Dtrace_events.c2542 struct ftrace_func_mapper *mapper = data; in event_enable_probe() local
2546 pdata = ftrace_func_mapper_find_ip(mapper, ip); in event_enable_probe()
2559 struct ftrace_func_mapper *mapper = data; in event_enable_count_probe() local
2563 pdata = ftrace_func_mapper_find_ip(mapper, ip); in event_enable_count_probe()
2586 struct ftrace_func_mapper *mapper = data; in event_enable_print() local
2590 pdata = ftrace_func_mapper_find_ip(mapper, ip); in event_enable_print()
2616 struct ftrace_func_mapper *mapper = *data; in event_enable_init() local
2620 if (!mapper) { in event_enable_init()
2621 mapper = allocate_ftrace_func_mapper(); in event_enable_init()
2622 if (!mapper) in event_enable_init()
[all …]
Dtrace.h996 void **ftrace_func_mapper_find_ip(struct ftrace_func_mapper *mapper,
998 int ftrace_func_mapper_add_ip(struct ftrace_func_mapper *mapper,
1000 void *ftrace_func_mapper_remove_ip(struct ftrace_func_mapper *mapper,
1002 void free_ftrace_func_mapper(struct ftrace_func_mapper *mapper,
Dftrace.c4122 void **ftrace_func_mapper_find_ip(struct ftrace_func_mapper *mapper, in ftrace_func_mapper_find_ip() argument
4128 entry = ftrace_lookup_ip(&mapper->hash, ip); in ftrace_func_mapper_find_ip()
4144 int ftrace_func_mapper_add_ip(struct ftrace_func_mapper *mapper, in ftrace_func_mapper_add_ip() argument
4150 entry = ftrace_lookup_ip(&mapper->hash, ip); in ftrace_func_mapper_add_ip()
4161 __add_hash_entry(&mapper->hash, &map->entry); in ftrace_func_mapper_add_ip()
4176 void *ftrace_func_mapper_remove_ip(struct ftrace_func_mapper *mapper, in ftrace_func_mapper_remove_ip() argument
4183 entry = ftrace_lookup_ip(&mapper->hash, ip); in ftrace_func_mapper_remove_ip()
4190 remove_hash_entry(&mapper->hash, entry); in ftrace_func_mapper_remove_ip()
4204 void free_ftrace_func_mapper(struct ftrace_func_mapper *mapper, in free_ftrace_func_mapper() argument
4210 int size = 1 << mapper->hash.size_bits; in free_ftrace_func_mapper()
[all …]
/Linux-v4.19/Documentation/device-mapper/
Ddm-uevent.txt1 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.
Dunstriped.txt4 The device-mapper "unstriped" target provides a transparent mechanism to
5 unstripe a device-mapper "striped" target to access the underlying disks
59 echo "0 1 unstriped ${NUM} ${CHUNK} ${i} /dev/mapper/raid0 0" | dmsetup create set-${i}
63 dd if=/dev/urandom of=/dev/mapper/set-${i} bs=${BS} count=${COUNT} oflag=direct
64 diff /dev/mapper/set-${i} member-${i}
103 to get a 92% reduction in read latency using this device mapper target.
116 /dev/mapper/nvmset0
117 /dev/mapper/nvmset1
121 dmsetup create raid_disk0 --table '0 512 unstriped 4 256 0 /dev/mapper/striped 0'
122 dmsetup create raid_disk1 --table '0 512 unstriped 4 256 1 /dev/mapper/striped 0'
[all …]
Dsnapshot.txt1 Device-mapper snapshot support
4 Device-mapper allows you, without massive data copying:
100 # ls -lL /dev/mapper/volumeGroup-*
101 brw------- 1 root root 254, 11 29 ago 18:15 /dev/mapper/volumeGroup-base-real
102 brw------- 1 root root 254, 12 29 ago 18:15 /dev/mapper/volumeGroup-snap-cow
103 brw------- 1 root root 254, 13 29 ago 18:15 /dev/mapper/volumeGroup-snap
104 brw------- 1 root root 254, 10 29 ago 18:14 /dev/mapper/volumeGroup-base
129 # ls -lL /dev/mapper/volumeGroup-*
130 brw------- 1 root root 254, 11 29 ago 18:15 /dev/mapper/volumeGroup-base-real
131 brw------- 1 root root 254, 12 29 ago 18:16 /dev/mapper/volumeGroup-base-cow
[all …]
Ddm-log.txt3 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
Dthin-provisioning.txt4 This document describes a collection of device-mapper targets that
42 a Red Hat distribution it is named 'device-mapper-persistent-data').
48 They use the dmsetup program to control the device-mapper driver
61 - Device-mapper 'messages' from userspace which control the creation of new
157 active pool device, /dev/mapper/pool in this example.
159 dmsetup message /dev/mapper/pool 0 "create_thin 0"
169 dmsetup create thin --table "0 2097152 thin /dev/mapper/pool 0"
184 dmsetup suspend /dev/mapper/thin
185 dmsetup message /dev/mapper/pool 0 "create_snap 1 0"
186 dmsetup resume /dev/mapper/thin
[all …]
Dcache.txt4 dm-cache is a device mapper target written by Joe Thornber, Heinz
11 This device-mapper solution allows us to insert this caching at
152 need a generic way of getting and setting these. Device-mapper
271 need a generic way of getting and setting these. Device-mapper
302 https://github.com/jthornber/device-mapper-test-suite
304 dmsetup create my_cache --table '0 41943040 cache /dev/mapper/metadata \
305 /dev/mapper/ssd /dev/mapper/origin 512 1 writeback default 0'
306 dmsetup create my_cache --table '0 41943040 cache /dev/mapper/metadata \
307 /dev/mapper/ssd /dev/mapper/origin 1024 1 writeback \
Dlog-writes.txt80 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
Dzero.txt31 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
Dswitch.txt4 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
Dpersistent-data.txt4 The more-sophisticated device-mapper targets require complex metadata
17 framework for people who want to store metadata in device-mapper
Ddm-queue-length.txt4 dm-queue-length is a path selector module for device-mapper targets,
Ddm-service-time.txt4 dm-service-time is a path selector module for device-mapper targets,
/Linux-v4.19/Documentation/ABI/testing/
Dsysfs-block-dm5 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.
Dsysfs-bus-iio-light-lm3533-als60 These values correspond to the ALS-mapper target registers for
61 ALS-mapper Y + 1.
/Linux-v4.19/Documentation/power/
Dswsusp-dmcrypt.txt34 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-v4.19/drivers/md/persistent-data/
DKconfig8 device-mapper targets such as the thin provisioning target.
/Linux-v4.19/drivers/md/
DKconfig202 tristate "Device mapper support"
206 Device-mapper is a low level volume manager. It works by allowing
230 bool "Device mapper debugging support"
233 Enable this for messages that may help debug device-mapper problems.
267 Some bio locking schemes used by other device-mapper targets
285 This device-mapper target allows you to create a device that
469 This device-mapper target creates a read-only device that
498 This device-mapper target creates a device that supports an arbitrary
512 This device-mapper target takes two devices, one device to use
532 This device-mapper target emulates a block device that has
[all …]
/Linux-v4.19/net/ceph/
DMakefile10 osd_client.o osdmap.o crush/crush.o crush/mapper.o crush/hash.o \
/Linux-v4.19/Documentation/filesystems/nfs/
Didmapper.txt5 Id mapper is used by NFS to translate user and group ids into names, and to
38 id mapper uses for key descriptions:
/Linux-v4.19/drivers/staging/android/ion/
Dion.h122 int (*map_user)(struct ion_heap *mapper, struct ion_buffer *buffer,

12