Home
last modified time | relevance | path

Searched refs:IO (Results 1 – 25 of 397) sorted by relevance

12345678910>>...16

/Linux-v5.10/arch/alpha/kernel/
Dmachvec_impl.h98 #define IO(UP,low) \ macro
103 #define DO_APECS_IO IO(APECS,apecs)
104 #define DO_CIA_IO IO(CIA,cia)
105 #define DO_IRONGATE_IO IO(IRONGATE,irongate)
106 #define DO_LCA_IO IO(LCA,lca)
107 #define DO_MARVEL_IO IO(MARVEL,marvel)
108 #define DO_MCPCIA_IO IO(MCPCIA,mcpcia)
109 #define DO_POLARIS_IO IO(POLARIS,polaris)
110 #define DO_T2_IO IO(T2,t2)
111 #define DO_TSUNAMI_IO IO(TSUNAMI,tsunami)
[all …]
/Linux-v5.10/Documentation/x86/i386/
DIO-APIC.rst4 IO-APIC
9 Most (all) Intel-MP compliant SMP boards have the so-called 'IO-APIC',
12 IO-APIC, interrupts from hardware will be delivered only to the
16 multiple IO-APICs. Multiple IO-APICs are used in high-end servers to
23 If your box boots fine with enabled IO-APIC IRQs, then your
28 0: 1360293 IO-APIC-edge timer
29 1: 4 IO-APIC-edge keyboard
32 14: 1448 IO-APIC-edge ide0
33 16: 28232 IO-APIC-level Intel EtherExpress Pro 10/100 Ethernet
34 17: 51304 IO-APIC-level eth0
[all …]
/Linux-v5.10/Documentation/block/
Dblk-mq.rst4 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 …]
/Linux-v5.10/Documentation/PCI/
Dboot-interrupts.rst13 interrupt messages (Assert_INTx/Deassert_INTx). The integrated IO-APIC in a
14 given Core IO converts the legacy interrupt messages from PCI Express to
15 MSI interrupts. If the IO-APIC is disabled (via the mask bits in the
16 IO-APIC table entries), the messages are routed to the legacy PCH. This
18 did not support the IO-APIC and for boot. Intel in the past has used the
22 describe problems with the Core IO handling of INTx message routing to the
79 Starting with ICX there are no longer any IO-APICs in the Core IO's
80 devices. IO-APIC is only in the PCH. Devices connected to the Core IO's
105 PCH - they are either converted into MSI via the integrated IO-APIC
106 (if the IO-APIC mask bit is clear in the appropriate entries)
/Linux-v5.10/Documentation/fb/
Ddeferred_io.rst2 Deferred IO
5 Deferred IO is a way to delay and repurpose IO. It uses host memory as a
7 IO. The following example may be a useful explanation of how one such setup
11 - deferred IO and driver sets up fault and page_mkwrite handlers
62 2. Setup your deferred IO callback. Eg::
67 The deferred_io callback is where you would perform all your IO to the display
/Linux-v5.10/drivers/net/ethernet/amd/
Datarilance.c234 #define DREG IO->data
235 #define AREG IO->addr
474 struct lance_ioreg *IO; in lance_probe1() local
534 IO = lp->iobase = (struct lance_ioreg *)ioaddr; in lance_probe1()
542 if (addr_accessible( &(IO->eeprom), 0, 0 )) { in lance_probe1()
544 i = IO->mem; in lance_probe1()
595 i = IO->eeprom; in lance_probe1()
600 i = IO->mem; in lance_probe1()
625 IO->ivec = IRQ_SOURCE_TO_VECTOR(dev->irq); in lance_probe1()
644 struct lance_ioreg *IO = lp->iobase; in lance_open() local
[all …]
/Linux-v5.10/block/
DKconfig100 the IO rate to a device. IO rate policies are per cgroup and
102 cgroups and specifying per device IO rate policies.
137 bool "Enable support for latency based cgroup IO protection"
140 Enabling this option enables the .latency interface for IO throttling.
141 The IO controller will attempt to maintain average IO latencies below
148 bool "Enable support for cost model based cgroup IO controller"
154 model based proportional IO control. The IO controller
155 distributes IO capacity between different groups based on
DKconfig.iosched4 menu "IO Schedulers"
10 MQ version of the deadline IO scheduler.
41 bool "BFQ IO controller debugging"
/Linux-v5.10/drivers/message/fusion/lsi/
Dmpi_history.txt88 * 03-11-05 01.05.07 Removed function codes for SCSI IO 32 and
91 * 06-24-05 01.05.08 Added function codes for SCSI IO 32 and
242 * Added Manufacturing pages, IO Unit Page 2, SCSI SPI
273 * Added IO Unit Page 3.
302 * Added structures for Manufacturing Page 4, IO Unit
364 * SAS IO Unit, SAS Expander, SAS Device, and SAS PHY.
368 * Two new bits defined for IO Unit Page 1 Flags field.
371 * Four new Flags bits defined for IO Unit Page 2.
372 * Added IO Unit Page 4.
379 * Added more defines for SAS IO Unit Page 0
[all …]
/Linux-v5.10/drivers/pci/hotplug/
Dibmphp_res.c98 case IO: in alloc_bus_range()
132 case IO: in alloc_bus_range()
257 rc = alloc_bus_range(&newbus, &newrange, curr, IO, 1); in ibmphp_rsrc_init()
265 rc = alloc_bus_range(&bus_cur, &newrange, curr, IO, 0); in ibmphp_rsrc_init()
270 rc = alloc_bus_range(&newbus, &newrange, curr, IO, 1); in ibmphp_rsrc_init()
329 new_io->type = IO; in ibmphp_rsrc_init()
384 case IO: in add_bus_range()
407 case IO: in add_bus_range()
457 case IO: in update_resources()
491 case IO: in fix_me()
[all …]
/Linux-v5.10/Documentation/ABI/testing/
Dconfigfs-iio6 This represents Industrial IO configuration entry point
14 Industrial IO software triggers directory.
27 Industrial IO software devices directory.
/Linux-v5.10/arch/arm/boot/dts/
Dsun7i-a20-bananapi.dts241 "TXD0", "RXD0", "IO-1", "PH3", "USB0-IDDET", "PH5", "", "",
243 "", "", "", "", "IO-4", "IO-5", "", "EMAC-PWR-EN",
246 "", "", "", "IO-GCLK", "", "", "", "",
249 "IO-6", "IO-3", "IO-2", "IO-0", "", "", "", "",
Darmada-xp-mv78460.dtsi93 0x81000000 0x1 0 MBUS_ID(0x04, 0xe0) 0 1 0 /* Port 0.0 IO */
95 0x81000000 0x2 0 MBUS_ID(0x04, 0xd0) 0 1 0 /* Port 0.1 IO */
97 0x81000000 0x3 0 MBUS_ID(0x04, 0xb0) 0 1 0 /* Port 0.2 IO */
99 0x81000000 0x4 0 MBUS_ID(0x04, 0x70) 0 1 0 /* Port 0.3 IO */
102 0x81000000 0x5 0 MBUS_ID(0x08, 0xe0) 0 1 0 /* Port 1.0 IO */
104 0x81000000 0x6 0 MBUS_ID(0x08, 0xd0) 0 1 0 /* Port 1.1 IO */
106 0x81000000 0x7 0 MBUS_ID(0x08, 0xb0) 0 1 0 /* Port 1.2 IO */
108 0x81000000 0x8 0 MBUS_ID(0x08, 0x70) 0 1 0 /* Port 1.3 IO */
111 0x81000000 0x9 0 MBUS_ID(0x04, 0xf0) 0 1 0 /* Port 2.0 IO */
114 0x81000000 0xa 0 MBUS_ID(0x08, 0xf0) 0 1 0 /* Port 3.0 IO */>;
Darmada-xp-mv78260.dtsi75 0x81000000 0x1 0 MBUS_ID(0x04, 0xe0) 0 1 0 /* Port 0.0 IO */
77 0x81000000 0x2 0 MBUS_ID(0x04, 0xd0) 0 1 0 /* Port 0.1 IO */
79 0x81000000 0x3 0 MBUS_ID(0x04, 0xb0) 0 1 0 /* Port 0.2 IO */
81 0x81000000 0x4 0 MBUS_ID(0x04, 0x70) 0 1 0 /* Port 0.3 IO */
84 0x81000000 0x5 0 MBUS_ID(0x08, 0xe0) 0 1 0 /* Port 1.0 IO */
86 0x81000000 0x6 0 MBUS_ID(0x08, 0xd0) 0 1 0 /* Port 1.1 IO */
88 0x81000000 0x7 0 MBUS_ID(0x08, 0xb0) 0 1 0 /* Port 1.2 IO */
90 0x81000000 0x8 0 MBUS_ID(0x08, 0x70) 0 1 0 /* Port 1.3 IO */
93 0x81000000 0x9 0 MBUS_ID(0x04, 0xf0) 0 1 0 /* Port 2.0 IO */>;
Domap-zoom-common.dtsi19 reg = <3 0 8>; /* CS3, offset 0, IO size 8 */
55 reg = <3 0x100 8>; /* CS3, offset 0x100, IO size 8 */
66 reg = <3 0x200 8>; /* CS3, offset 0x200, IO size 8 */
77 reg = <3 0x300 8>; /* CS3, offset 0x300, IO size 8 */
/Linux-v5.10/Documentation/admin-guide/cgroup-v1/
Dblkio-controller.rst2 Block IO Controller
8 a need of various kinds of IO control policies (like proportional BW, max BW)
11 and based on user options switch IO policies in the background.
13 One IO control policy is throttling policy which can be used to
14 specify upper IO rate limits on devices. This policy is implemented in
22 - Enable Block IO controller::
83 - Block IO controller.
165 may cause the service time for a given IO to include the service time
180 the IO is dispatched to the device but till it actually gets serviced
209 cumulative total of the amount of time spent by each IO in that cgroup
[all …]
/Linux-v5.10/Documentation/networking/device_drivers/ethernet/huawei/
Dhinic.rst63 card by AEQs. Also set the addresses of the IO CMDQs in HW.
66 IO components:
69 Completion Event Queues(CEQs) - The completion Event Queues that describe IO
77 Command Queues(CMDQ) - The queues for sending commands for IO management and is
85 IO - de/constructs all the IO components. (hinic_hw_io.c, hinic_hw_io.h)
91 initialization of the driver and the IO components on the case of Interface
/Linux-v5.10/drivers/infiniband/ulp/rtrs/
DREADME8 transport. It is optimized to transfer (read/write) IO blocks.
53 The new rkey is sent back to the client along with the IO result.
55 registration on each IO causes performance drop of up to 20%. A user of the
97 side or network outage in an absence of IO.
100 corresponding path is disconnected, all the inflight IO are failed over to a
117 IO path
131 inflight IO and for the error code.
145 first, when it finishes, pass the IO to RNBD server module.
149 inflight IO and for the error code. The new rkey is sent back using
151 the message and finished IO after update rkey for the rbuffer, then post
[all …]
/Linux-v5.10/tools/perf/Documentation/
Dperf-timechart.txt20 but it's possible to record IO (disk, network) activity using -I argument.
25 events or IO events.
27 In IO mode, every bar has two charts: upper and lower.
70 Don't draw EAGAIN IO events.
73 to see very small and fast IO. It's possible to specify ms or us
118 Record system-wide IO events:
/Linux-v5.10/Documentation/devicetree/bindings/pci/
Dmvebu-pci.txt108 0x81000000 0x1 0 MBUS_ID(0x04, 0xe0) 0 1 0 /* Port 0.0 IO */
110 0x81000000 0x2 0 MBUS_ID(0x04, 0xd0) 0 1 0 /* Port 0.1 IO */
112 0x81000000 0x3 0 MBUS_ID(0x04, 0xb0) 0 1 0 /* Port 0.2 IO */
114 0x81000000 0x4 0 MBUS_ID(0x04, 0x70) 0 1 0 /* Port 0.3 IO */
117 0x81000000 0x5 0 MBUS_ID(0x08, 0xe0) 0 1 0 /* Port 1.0 IO */
119 0x81000000 0x6 0 MBUS_ID(0x08, 0xd0) 0 1 0 /* Port 1.1 IO */
121 0x81000000 0x7 0 MBUS_ID(0x08, 0xb0) 0 1 0 /* Port 1.2 IO */
123 0x81000000 0x8 0 MBUS_ID(0x08, 0x70) 0 1 0 /* Port 1.3 IO */
126 0x81000000 0x9 0 MBUS_ID(0x04, 0xf0) 0 1 0 /* Port 2.0 IO */
129 0x81000000 0xa 0 MBUS_ID(0x08, 0xf0) 0 1 0 /* Port 3.0 IO */>;
/Linux-v5.10/Documentation/core-api/
Dgfp_mask-from-fs-io.rst4 GFP masks used from FS/IO context
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
36 mask so no memory allocation can recurse back in the FS/IO.
43 FS/IO code then simply calls the appropriate save function before
/Linux-v5.10/drivers/pinctrl/ti/
DKconfig10 Say Y here to support Texas Instruments' IO delay pinconf driver.
11 IO delay module is used for the DRA7 SoC family.
/Linux-v5.10/tools/io_uring/
DREADME8 for setting up an io_uring instance, submitting IO, completing IO,
15 fixed buffers, and polled IO. There are options in the program to
/Linux-v5.10/arch/x86/
DKconfig.debug134 prompt "IO delay type"
138 bool "port 0x80 based port-IO delay [recommended]"
140 This is the traditional Linux IO delay used for in/out_p.
144 bool "port 0xed based port-IO delay"
146 Use port 0xed as the IO delay. This frees up port 0x80 which is
150 bool "udelay based port-IO delay"
152 Use udelay(2) as the IO delay method. This provides the delay
153 while not having any side-effect on the IO port space.
156 bool "no port-IO delay"
158 No port-IO delay. Will break on old boxes that require port-IO
/Linux-v5.10/Documentation/devicetree/bindings/interrupt-controller/
Dintel,ce4100-ioapic.txt4 * Intel I/O Advanced Programmable Interrupt Controller (IO APIC)
16 IO APIC. The second number (S) represents the sense of interrupt which

12345678910>>...16