Searched full:io (Results 1 – 25 of 590) sorted by relevance
12345678910>>...24
| /Documentation/block/ |
| D | ublk.rst | 28 ublk block device (``/dev/ublkb*``) is added by ublk driver. Any IO request
37 After the IO is handled by userspace, the result is committed back to the
38 driver, thus completing the request cycle. This way, any specific IO handling
39 logic is totally done by userspace, such as loop's IO handling, NBD's IO
40 communication, or qcow2's IO mapping.
44 IO too, which is 1:1 mapped with IO of ``/dev/ublkb*``.
46 Both the IO request forward and IO handling result committing are done via
49 give better IOPS than block IO; which is why ublk is one of high performance
50 implementation of userspace block device: not only IO request communication is
51 done by io_uring, but also the preferred IO handling in ublk server is io_uring
[all …]
|
| D | ioprio.rst | 2 Block io priorities
9 With the introduction of cfq v3 (aka cfq-ts or time sliced cfq), basic io
10 priorities are supported for reads on files. This enables users to io nice
13 with cfq; other io schedulers do not support io priorities thus far.
18 CFQ implements three generic scheduling classes that determine how io is
21 IOPRIO_CLASS_RT: This is the realtime io class. This scheduling class is given
24 care, one io RT process can starve the entire system. Within the RT class,
31 for any process that hasn't set a specific io priority. The class data
32 determines how much io bandwidth the process will get, it's directly mappable
34 BE prio level, 7 is the lowest. The mapping between cpu nice level and io
[all …]
|
| D | blk-mq.rst | 4 Multi-Queue Block IO Queueing Mechanism (blk-mq)
7 The Multi-Queue Block IO Queueing Mechanism is an API to enable fast storage
9 through queueing and submitting IO requests to block devices simultaneously,
19 development of the kernel. The Block IO subsystem aimed to achieve the best
32 The former design had a single queue to store block IO requests with a single
36 to different CPUs) wanted to perform block IO. Instead of this, the blk-mq API
44 When the userspace performs IO to a block device (reading or writing a file,
45 for instance), blk-mq takes action: it will store and manage IO requests to
52 cases that it might not do that: if there's an IO scheduler attached at the
65 The block IO subsystem adds requests in the software staging queues
[all …]
|
| D | switching-sched.rst | 5 Each io queue has a set of io scheduler tunables associated with it. These
6 tunables control how the io scheduler works. You can find these entries
16 It is possible to change the IO scheduler for a given block device on
24 where SCHEDNAME is the name of a defined IO scheduler, and DEV is the
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-mlxreg-io | 1 What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/asic_health
10 What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld1_version
11 What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld2_version
20 What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/fan_dir
30 What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld3_version
39 What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/jtag_enable
48 What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/select_iio
59 What: /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/psu1_on
60 /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/psu2_on
61 /sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/pwr_cycle
[all …]
|
| /Documentation/devicetree/bindings/iio/multiplexer/ |
| D | io-channel-mux.yaml | 4 $id: http://devicetree.org/schemas/iio/multiplexer/io-channel-mux.yaml#
16 For each non-empty string in the channels property, an io-channel will be
17 created. The number of this io-channel is the same as the index into the list
25 const: io-channel-mux
27 io-channels:
31 io-channel-names:
48 "#io-channel-cells":
53 - io-channels
54 - io-channel-names
72 compatible = "io-channel-mux";
[all …]
|
| /Documentation/devicetree/bindings/power/ |
| D | rockchip-io-domain.yaml | 4 $id: http://devicetree.org/schemas/power/rockchip-io-domain.yaml#
7 title: Rockchip SRAM for IO Voltage Domains
13 IO domain voltages on some Rockchip SoCs are variable but need to be
42 to report their voltage. The IO Voltage Domain for any non-specified
48 - rockchip,px30-io-voltage-domain
49 - rockchip,px30-pmu-io-voltage-domain
50 - rockchip,rk3188-io-voltage-domain
51 - rockchip,rk3228-io-voltage-domain
52 - rockchip,rk3288-io-voltage-domain
53 - rockchip,rk3328-io-voltage-domain
[all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | canaan,k210-fpioa.yaml | 13 The Canaan Kendryte K210 SoC Fully Programmable IO Array (FPIOA)
15 48 IO pins of the SoC. Pin function configuration is performed on
62 List of IO pins alternate functions. The values for each IO
63 pin is a combination of an IO pin number (0 to 47) with the
64 desired function for the IO pin. Functions are defined as
66 The K210_FPIOA(IO pin, function) macro is provided to
67 facilitate the combination of IO pin numbers and functions.
85 List of IO pins affected by the properties specified in this
86 subnode. IO pins are identified using the pin names "IO_xx".
88 be used for the SoC pin groups A0 (IO pins 0-5),
[all …]
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | envelope-detector.yaml | 34 io-channels:
38 io-channel-names:
49 - io-channels
50 - io-channel-names
65 #io-channel-cells = <1>;
72 io-channels = <&dpot 0>;
73 io-channel-names = "dpot";
74 #io-channel-cells = <1>;
79 io-channels = <&dac 0>;
80 io-channel-names = "dac";
|
| /Documentation/devicetree/bindings/input/touchscreen/ |
| D | resistive-adc-touch.yaml | 24 io-channels:
33 io-channel-names:
62 - io-channels
63 - io-channel-names
69 io-channels = <&adc 24>, <&adc 25>;
70 io-channel-names = "y", "x";
76 io-channels = <&adc 24>, <&adc 25>, <&adc 26>;
77 io-channel-names = "y", "pressure", "x";
83 io-channels = <&adc 1>, <&adc 2>, <&adc 3>, <&adc 4>;
84 io-channel-names = "x", "z1", "z2", "y";
|
| /Documentation/devicetree/bindings/iio/afe/ |
| D | current-sense-shunt.yaml | 13 When an io-channel measures the voltage over a current sense shunt,
22 io-channels:
25 Channel node of a voltage io-channel.
27 "#io-channel-cells":
35 - io-channels
48 #io-channel-cells = <1>;
62 io-channels = <&tiadc 0>;
63 #io-channel-cells = <0>;
|
| D | voltage-divider.yaml | 13 When an io-channel measures the midpoint of a voltage divider, the
37 io-channels:
40 Channel node of a voltage io-channel.
48 Resistance R + Rout for the full divider. The io-channel is scaled by
53 - io-channels
72 #io-channel-cells = <1>;
80 io-channels = <&maxadc 1>;
|
| D | temperature-transducer.yaml | 19 When an io-channel measures the output voltage of a temperature analog front
56 io-channels:
59 Channel node of a voltage io-channel.
61 '#io-channel-cells':
91 - io-channels
98 #io-channel-cells = <0>;
99 io-channels = <&temp_adc 3>;
108 #io-channel-cells = <0>;
109 io-channels = <&temp_adc 2>;
|
| D | current-sense-amplifier.yaml | 13 When an io-channel measures the output voltage from a current sense
22 io-channels:
25 Channel node of a voltage io-channel.
40 - io-channels
49 io-channels = <&tiadc 0>;
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | nokia,n900-battery.yaml | 20 io-channels:
26 io-channel-names:
34 - io-channels
35 - io-channel-names
43 io-channels = <&twl4030_madc 0>,
46 io-channel-names = "temp",
|
| D | lego,ev3-battery.yaml | 25 io-channels:
30 io-channel-names:
41 - io-channels
42 - io-channel-names
52 io-channels = <&adc 4>, <&adc 3>;
53 io-channel-names = "voltage", "current";
|
| D | ingenic,battery.yaml | 25 io-channels:
28 io-channel-names:
40 - io-channels
41 - io-channel-names
58 io-channels = <&adc INGENIC_ADC_BATTERY>;
59 io-channel-names = "battery";
|
| D | stericsson,ab8500-btemp.yaml | 39 io-channels:
42 io-channel-names:
52 - io-channels
53 - io-channel-names
74 io-channels = <&gpadc 0x02>, <&gpadc 0x01>;
75 io-channel-names = "btemp_ball", "bat_ctrl";
|
| D | adc-battery.yaml | 36 io-channels:
40 io-channel-names:
52 - io-channels
53 - io-channel-names
65 io-channels = <&adc 13>, <&adc 37>;
66 io-channel-names = "voltage", "current";
|
| D | stericsson,ab8500-fg.yaml | 44 io-channels:
47 io-channel-names:
56 - io-channels
57 - io-channel-names
78 io-channels = <&gpadc 0x08>;
79 io-channel-names = "main_bat_v";
|
| D | qcom,pmi8998-charger.yaml | 31 io-channels:
36 io-channel-names:
50 - io-channels
51 - io-channel-names
75 io-channels = <&pmi8998_rradc 3>,
77 io-channel-names = "usbin_i",
|
| /Documentation/devicetree/bindings/iio/dac/ |
| D | dpot-dac.yaml | 37 io-channels:
42 io-channel-names:
45 "#io-channel-cells":
51 - io-channels
52 - io-channel-names
61 io-channels = <&dpot 0>;
62 io-channel-names = "dpot";
|
| /Documentation/devicetree/bindings/sound/ |
| D | audio-iio-aux.yaml | 22 io-channels:
26 io-channel-names:
28 Industrial I/O channel names related to io-channels.
51 - io-channels
52 - io-channel-names
60 io-channels = <&iio 0>, <&iio 1>, <&iio 2>, <&iio 3>;
61 io-channel-names = "CH0", "CH1", "CH2", "CH3";
|
| /Documentation/devicetree/bindings/memory-controllers/ddr/ |
| D | jedec,lpddr-channel.yaml | 26 io-width:
29 from (a multiple of) the io-width of the LPDDR chip, that means that
35 connected LPDDR chip, times the io-width of the channel divided by
36 the io-width of the LPDDR chip.
102 - io-width
114 io-width = <32>;
120 io-width = <16>;
129 io-width = <32>;
135 io-width = <32>;
143 io-width = <32>;
|
| /Documentation/admin-guide/blockdev/drbd/ |
| D | disk-states-8.dot | 11 Consistent -> Failed [ label = "io completion error" ]
12 Outdated -> Failed [ label = "io completion error" ]
13 UpToDate -> Failed [ label = "io completion error" ]
14 Inconsistent -> Failed [ label = "io completion error" ]
|
12345678910>>...24