/linux-6.6.21/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 | 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 …]
|
/linux-6.6.21/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 …]
|
/linux-6.6.21/arch/alpha/kernel/ |
D | machvec_impl.h | 100 #define IO(UP,low) \ macro 105 #define DO_APECS_IO IO(APECS,apecs) 106 #define DO_CIA_IO IO(CIA,cia) 107 #define DO_IRONGATE_IO IO(IRONGATE,irongate) 108 #define DO_LCA_IO IO(LCA,lca) 109 #define DO_MARVEL_IO IO(MARVEL,marvel) 110 #define DO_MCPCIA_IO IO(MCPCIA,mcpcia) 111 #define DO_POLARIS_IO IO(POLARIS,polaris) 112 #define DO_T2_IO IO(T2,t2) 113 #define DO_TSUNAMI_IO IO(TSUNAMI,tsunami) [all …]
|
/linux-6.6.21/drivers/scsi/pm8001/ |
D | pm80xx_hwi.c | 110 pm8001_dbg(pm8001_ha, IO, in pm80xx_get_fatal_dump() 124 pm8001_dbg(pm8001_ha, IO, "ossaHwCB: status1 %d\n", status); in pm80xx_get_fatal_dump() 125 pm8001_dbg(pm8001_ha, IO, "ossaHwCB: read_len 0x%x\n", in pm80xx_get_fatal_dump() 127 pm8001_dbg(pm8001_ha, IO, "ossaHwCB: direct_len 0x%x\n", in pm80xx_get_fatal_dump() 129 pm8001_dbg(pm8001_ha, IO, "ossaHwCB: direct_offset 0x%x\n", in pm80xx_get_fatal_dump() 150 pm8001_dbg(pm8001_ha, IO, "get_fatal_spcv: accum_len 0x%x\n", in pm80xx_get_fatal_dump() 152 pm8001_dbg(pm8001_ha, IO, "get_fatal_spcv: length_to_read 0x%x\n", in pm80xx_get_fatal_dump() 154 pm8001_dbg(pm8001_ha, IO, "get_fatal_spcv: last_offset 0x%x\n", in pm80xx_get_fatal_dump() 156 pm8001_dbg(pm8001_ha, IO, "get_fatal_spcv: read_len 0x%x\n", in pm80xx_get_fatal_dump() 158 pm8001_dbg(pm8001_ha, IO, "get_fatal_spcv:: direct_len 0x%x\n", in pm80xx_get_fatal_dump() [all …]
|
D | pm8001_hwi.c | 1343 pm8001_dbg(pm8001_ha, IO, "No free mpi buffer\n"); in pm8001_mpi_build_cmd() 1406 pm8001_dbg(pm8001_ha, IO, " CI=%d PI=%d\n", in pm8001_mpi_msg_free_set() 1449 pm8001_dbg(pm8001_ha, IO, in pm8001_mpi_msg_consume() 1589 pm8001_dbg(pm8001_ha, IO, "IO_XFER_OPEN_RETRY_TIMEOUT\n"); in pm8001_work_fn() 1594 pm8001_dbg(pm8001_ha, IO, "...Task on lu\n"); in pm8001_work_fn() 1596 pm8001_dbg(pm8001_ha, IO, "...Task NOT on lu\n"); in pm8001_work_fn() 1643 pm8001_dbg(pm8001_ha, IO, "...Reset phy\n"); in pm8001_work_fn() 1657 pm8001_dbg(pm8001_ha, IO, "...Reset phy\n"); in pm8001_work_fn() 1664 pm8001_dbg(pm8001_ha, IO, "...Complete\n"); in pm8001_work_fn() 1814 pm8001_dbg(pm8001_ha, IO, "IO_SUCCESS,param = %d\n", in mpi_ssp_completion() [all …]
|
/linux-6.6.21/Documentation/translations/zh_CN/core-api/ |
D | gfp_mask-from-fs-io.rst | 16 从FS/IO上下文中使用的GFP掩码 25 文件系统和IO栈中的代码路径在分配内存时必须小心,以防止因直接调用FS或IO路径的内 42 没有内存分配可以追溯到FS/IO中。 49 然后,FS/IO代码在任何与回收有关的关键部分开始之前简单地调用适当的保存函数
|
/linux-6.6.21/Documentation/arch/x86/i386/ |
D | IO-APIC.rst | 4 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-6.6.21/Documentation/PCI/ |
D | boot-interrupts.rst | 13 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-6.6.21/Documentation/fb/ |
D | deferred_io.rst | 2 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-6.6.21/Documentation/translations/zh_CN/PCI/ |
D | pci.rst | 241 后确定MMIO和IO端口资源的可用性。 244 范围)和 ``request_region()`` (用于IO端口范围)。对于那些不被 "正常 "PCI BAR描 337 - 禁用设备对MMIO/IO端口地址的响应 338 - 释放MMIO/IO端口资源 390 禁止设备对MMIO/IO端口地址做出响应 392 io_unmap() MMIO或IO端口资源,然后调用pci_disable_device()。 397 释放MMIO/IO端口资源 399 调用pci_release_region()来标记MMIO或IO端口范围为可用。
|
/linux-6.6.21/drivers/net/ethernet/amd/ |
D | atarilance.c | 234 #define DREG IO->data 235 #define AREG IO->addr 470 struct lance_ioreg *IO; in lance_probe1() local 531 IO = lp->iobase = (struct lance_ioreg *)ioaddr; in lance_probe1() 539 if (addr_accessible( &(IO->eeprom), 0, 0 )) { in lance_probe1() 541 i = IO->mem; in lance_probe1() 593 i = IO->eeprom; in lance_probe1() 599 i = IO->mem; in lance_probe1() 624 IO->ivec = IRQ_SOURCE_TO_VECTOR(dev->irq); in lance_probe1() 643 struct lance_ioreg *IO = lp->iobase; in lance_open() local [all …]
|
/linux-6.6.21/drivers/message/fusion/lsi/ |
D | mpi_history.txt | 88 * 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-6.6.21/drivers/pci/hotplug/ |
D | ibmphp_res.c | 98 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-6.6.21/block/ |
D | Kconfig | 97 the IO rate to a device. IO rate policies are per cgroup and 99 cgroups and specifying per device IO rate policies. 131 bool "Enable support for latency based cgroup IO protection" 134 Enabling this option enables the .latency interface for IO throttling. 135 The IO controller will attempt to maintain average IO latencies below 151 bool "Enable support for cost model based cgroup IO controller" 156 model based proportional IO control. The IO controller 157 distributes IO capacity between different groups based on
|
/linux-6.6.21/arch/arm/boot/dts/allwinner/ |
D | sun7i-a20-bananapi.dts | 240 "TXD0", "RXD0", "IO-1", "PH3", "USB0-IDDET", "PH5", "", "", 242 "", "", "", "", "IO-4", "IO-5", "", "EMAC-PWR-EN", 245 "", "", "", "IO-GCLK", "", "", "", "", 248 "IO-6", "IO-3", "IO-2", "IO-0", "", "", "", "",
|
/linux-6.6.21/Documentation/ABI/testing/ |
D | configfs-iio | 6 This represents Industrial IO configuration entry point 14 Industrial IO software triggers directory. 27 Industrial IO software devices directory.
|
/linux-6.6.21/Documentation/admin-guide/cgroup-v1/ |
D | blkio-controller.rst | 2 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 23 Enable Block IO controller:: 85 Block IO controller. 170 may cause the service time for a given IO to include the service time 185 the IO is dispatched to the device but till it actually gets serviced 214 cumulative total of the amount of time spent by each IO in that cgroup [all …]
|
/linux-6.6.21/Documentation/translations/zh_CN/mm/ |
D | numa.rst | 19 本地内存和/或IO总线。为了简洁起见,并将这些物理组件/装配的硬件视角与软件抽象区分开来,我们在 31 内存访问时间和有效的内存带宽取决于包含CPU的单元或进行内存访问的IO总线距离包含目标内存的单元 42 上,对一些架构的细节进行了抽象。与物理单元一样,软件节点可能包含0或更多的CPU、内存和/或IO
|
/linux-6.6.21/Documentation/networking/device_drivers/ethernet/huawei/ |
D | hinic.rst | 63 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-6.6.21/drivers/infiniband/ulp/rtrs/ |
D | README | 8 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-6.6.21/tools/perf/Documentation/ |
D | perf-timechart.txt | 20 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-6.6.21/arch/arm/boot/dts/ti/omap/ |
D | omap-zoom-common.dtsi | 19 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-6.6.21/Documentation/translations/zh_CN/accounting/ |
D | delay-accounting.rst | 94 IO count delay total delay average 107 获取pid为1的IO计数,它只和-p一起使用:: 109 printing IO accounting
|
/linux-6.6.21/arch/arm/boot/dts/marvell/ |
D | armada-xp-mv78460.dtsi | 93 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 */>;
|