Searched full:paths (Results 1 – 25 of 155) sorted by relevance
1234567
| /Documentation/admin-guide/device-mapper/ |
| D | dm-service-time.rst | 11 The performance value is a relative throughput value among all paths
26 among all paths in the path-group.
30 other paths having a positive value are available.
43 among all paths in the path-group.
59 1. If the paths have the same 'relative_throughput', skip
62 2. If the paths have the same 'in-flight-size', skip the division
65 3. If some paths have non-zero 'relative_throughput' and others
66 have zero 'relative_throughput', ignore those paths with zero
78 In case that 2 paths (sda and sdb) are used with repeat_count == 128
|
| D | switch.rst | 7 paths. The path used for any specific region can be switched
38 robin algorithm to send I/O across all paths and let the storage array
52 Lower Tier - Load balance amongst paths to a particular member.
55 Each of these multipath devices contains the set of paths directly to
57 selectors to load balance amongst these paths. We also build a
58 non-preferred priority group containing paths to other array members for
73 The number of paths across which to distribute the I/O.
77 to any of the available paths.
97 which paths.
|
| D | dm-queue-length.rst | 37 In case that 2 paths (sda and sdb) are used with repeat_count == 128.
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-rtrs-server | 8 What: /sys/class/rtrs-server/<session-name>/paths/
16 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/disconnect
23 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/hca_name
29 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/hca_port
35 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/src_addr
41 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/dst_addr
47 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/stats/rdma
|
| D | sysfs-class-rtrs-client | 40 What: /sys/class/rtrs-client/<session-name>/paths/
48 What: /sys/class/rtrs-client/<session-name>/paths/<src@dst>/state
55 What: /sys/class/rtrs-client/<session-name>/paths/<src@dst>/reconnect
62 What: /sys/class/rtrs-client/<session-name>/paths/<src@dst>/disconnect
69 What: /sys/class/rtrs-client/<session-name>/paths/<src@dst>/remove_path
77 What: /sys/class/rtrs-client/<session-name>/paths/<src@dst>/hca_name
83 What: /sys/class/rtrs-client/<session-name>/paths/<src@dst>/hca_port
89 What: /sys/class/rtrs-client/<session-name>/paths/<src@dst>/src_addr
95 What: /sys/class/rtrs-client/<session-name>/paths/<src@dst>/dst_addr
101 What: /sys/class/rtrs-client/<session-name>/paths/<src@dst>/cur_latency
[all …]
|
| /Documentation/driver-api/firmware/ |
| D | direct-fs-lookup.rst | 7 filesystem in the paths documented in the section 'Firmware search paths'.
12 It is recommended you keep /lib/firmware paths on your root filesystem,
|
| D | fw_search_path.rst | 2 Firmware search paths
5 The following search paths are used to look for firmware on your
|
| /Documentation/devicetree/bindings/interconnect/ |
| D | interconnect.txt | 40 bandwidth requirements along interconnect paths they are connected to. There
42 multiple paths from different providers depending on use case and the
56 interconnect-names to match interconnect paths with interconnect
|
| /Documentation/trace/coresight/ |
| D | coresight-dummy.rst | 17 not have any programming interfaces, so that paths can be created in the driver.
19 disabling them. It also provides the Coresight dummy sink/source paths for
|
| /Documentation/filesystems/iomap/ |
| D | porting.rst | 68 functions for selected call paths.
79 ``SEEK_HOLE`` before tackling the I/O paths.
82 The buffered read I/O paths doesn't need to be converted yet, though the
104 Most likely at this point, the buffered read and write paths will still
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,coresight-dummy-source.yaml | 21 is needed to register them as Coresight source devices, so that paths can be
24 Coresight dummy source paths for debugging.
|
| /Documentation/networking/ |
| D | mptcp.rst | 16 paths.
25 Thanks to MPTCP, being able to use multiple paths in parallel or simultaneously
33 - Network aggregation: using multiple paths at the same time to have a higher
72 (paths), the default in-kernel MPTCP path-manager needs to know which IP
|
| /Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 13 Code paths in the filesystem and IO stacks must be careful when
15 memory reclaim calling back into the FS or IO paths and blocking on
|
| /Documentation/driver-api/ |
| D | interconnect.rst | 72 Interconnect consumers are the entities which make use of the data paths exposed
91 get paths between endpoints and set their bandwidth/latency/QoS requirements
92 for these interconnect paths. These interfaces are not currently
138 # Voting for multiple paths is possible by repeating this
|
| /Documentation/sound/soc/ |
| D | dapm.rst | 57 audio subsystem signal paths
182 audio paths within the audio subsystem. They have the following form:
251 This can be used to merge two signal paths together in software.
302 audio paths (called interconnections). Each interconnection must be defined in
303 order to create a graph of all audio paths between widgets.
307 paths.
|
| /Documentation/firmware-guide/acpi/ |
| D | osi.rst | 30 Experience shows that taking untested paths through the BIOS
143 catastrophic failure resulting from the BIOS taking paths that
174 to the hardware and validated BIOS paths seen by OSX.
181 from going down untested combinations of paths.
|
| /Documentation/arch/x86/ |
| D | orc-unwinder.rst | 19 all the code paths of a .o file, it determines information about the
95 paths, and so it already has all the information it needs to be able to
104 That could be rectified by manually annotating those special code paths
144 the code paths of a .o file, it creates an array of orc_entry structs,
|
| /Documentation/userspace-api/gpio/ |
| D | sysfs.rst | 43 Paths in Sysfs
72 GPIO signals have paths like /sys/class/gpio/gpio42/ (for GPIO #42)
121 GPIO controllers have paths like /sys/class/gpio/gpiochip42/ (for the
|
| /Documentation/devicetree/bindings/sound/ |
| D | sound-card-common.yaml | 24 Paths between these endpoints are still active over suspend of the main
|
| /Documentation/process/ |
| D | botching-up-ioctls.rst | 84 Fun with Error Paths
89 error handling paths - GPUs will die eventually in the oddmost corner cases
107 this will allow you to test 90% of all error handling paths by just
110 paths pretty much for free for graphics drivers. Also, be consistent with
|
| /Documentation/virt/ |
| D | paravirt_ops.rst | 34 because they include sensitive instructions or some code paths in
|
| /Documentation/devicetree/bindings/display/tegra/ |
| D | nvidia,tegra124-vic.yaml | 59 description: Description of the interconnect paths for the VIC;
|
| D | nvidia,tegra186-dc.yaml | 51 description: Description of the interconnect paths for the
|
| /Documentation/devicetree/bindings/misc/ |
| D | ti,j721e-esm.yaml | 16 controller would do. The safety signals have their separate paths within
|
| /Documentation/mm/ |
| D | remap_file_pages.rst | 13 code in kernel virtual memory subsystem including hot paths. Also to get
|
1234567