Searched refs:O (Results 51 – 75 of 1468) sorted by relevance
12345678910>>...59
17 to or from user memory, so this I/O method is not necessarily less22 However this is also the simplest I/O method, requiring little or no33 must implement one I/O method if they exchange data with applications,40 supporting all I/O interfaces, but as much as the complex memory41 mapping I/O can be inadequate for some devices we have no reason to
13 VIDIOC_REQBUFS - Initiate Memory Mapping, User Pointer I/O or DMA buffer I/O35 :ref:`user pointer <userp>` or :ref:`DMABUF <dmabuf>` based I/O.39 ioctl is merely used to switch the driver into user pointer I/O mode and42 configures the driver into DMABUF I/O mode without performing any direct49 I/O method and the ``reserved`` array must be zeroed. When the ioctl is58 When the I/O method is not supported the ioctl returns an ``EINVAL`` error163 queue is used for :ref:`memory mapping <mmap>` streaming I/O. See180 The buffer type (``type`` field) or the requested I/O method
23 # GNU 'C' compiler Linux build with threads, largefiles, async I/O 32 # GNU 'C' compiler Linux build for powerpc chip with threads, largefiles, async I/O 41 # GNU 'C' compiler Linux build for sparc chip with threads, largefiles, async I/O 50 # GNU 'C' compiler Linux build with threads, largefiles, async I/O 59 # GNU 'C' compiler Linux build for powerpc chip with threads, largefiles, async I/O 68 # GNU 'C' compiler Linux build with threads, largefiles, async I/O77 # GNU 'C' compiler Linux build with threads, largefiles, async I/O 86 # GNU 'C' compiler Linux build with S/390, threads, largfiles, async I/O95 # GNU 'C' compiler Linux build with S/390, threads, largfiles, async I/O
48 …ata_is_ptr, uint64_t addr, uint64_t data, uint32_t count, uint32_t size) "I/O=%p type=%d dir=%d df…49 …ata_is_ptr, uint64_t addr, uint64_t data, uint32_t count, uint32_t size) "I/O=%p read type=%d df=%…50 …ata_is_ptr, uint64_t addr, uint64_t data, uint32_t count, uint32_t size) "I/O=%p write type=%d df=…51 …ata_is_ptr, uint64_t addr, uint64_t data, uint32_t count, uint32_t size) "I/O=%p pio dir=%d df=%d …52 cpu_ioreq_pio_read_reg(void *req, uint64_t data, uint64_t addr, uint32_t size) "I/O=%p pio read reg…53 cpu_ioreq_pio_write_reg(void *req, uint64_t data, uint64_t addr, uint32_t size) "I/O=%p pio write r…54 …ata_is_ptr, uint64_t addr, uint64_t data, uint32_t count, uint32_t size) "I/O=%p copy dir=%d df=%d…56 cpu_ioreq_config_read(void *req, uint32_t sbdf, uint32_t reg, uint32_t size, uint32_t data) "I/O=%p…57 cpu_ioreq_config_write(void *req, uint32_t sbdf, uint32_t reg, uint32_t size, uint32_t data) "I/O=%…
7 title: Intel I/O Advanced Programmable Interrupt Controller (IO APIC)16 into the processor itself and an external I/O APIC. Local APIC18 from internal sources and from an external I/O APIC (ioapic).26 This schema defines bindings for I/O APIC interrupt controller.
29 DEBUG_OPTIMIZATION:append:mips = " -O"31 BUILD_OPTIMIZATION:append:mips = " -O"34 DEBUG_OPTIMIZATION:append:mipsel = " -O"36 BUILD_OPTIMIZATION:append:mipsel = " -O"
47 rmap链表变得过大。rmap的遍历具有O(N)的复杂度，其中N是共享页面的rmap_项（即49 因此，这有效地将线性O(N)计算复杂度从rmap遍历中分散到不同的KSM页面上。ksmd进50 程在稳定节点"链"上的遍历也是O(N)，但这个N是稳定树"副本"的数量，而不是rmap项
6 controller, which were used for isochronous I/O. It was added as an7 alternative to raw1394's isochronous I/O functionality which had10 asynchronous I/O for device discovery and configuration.
1vhdxfileQ�E�M�U� �v�1�.�6�.�5�
59 If you build your kernel using KBUILD_OUTPUT= or O= options, these62 O=<kernel_build_path> $0 -- ./test_progs -t test_lsm390 if is_rel_path "${O}"; then391 O="$(realpath "${PWD}/${O}")"393 kernel_bzimage="${O}/${BZIMAGE}"394 make_command="${make_command} O=${O}"
37 ifneq ($(O),)38 FULL_O := $(shell cd $(PWD); readlink -f $(O) || echo $(O))
68 fn make_closure<F, O, E>(self, f: F) -> F in make_closure() argument70 F: FnOnce(*mut Self::Datee) -> Result<O, E>, in make_closure() argument97 fn make_closure<F, O, E>(self, f: F) -> F in make_closure() argument99 F: FnOnce(*mut Self::Datee) -> Result<O, E>, in make_closure() argument
55 volatile的存储类型最初是为那些内存映射的I/O寄存器而定义。在内核里，寄存器访问也应56 该被锁保护，但是人们也不希望编译器“优化”临界区内的寄存器访问。内核里I/O的内存访问57 是通过访问函数完成的；不赞成通过指针对I/O内存的直接访问，并且不是在所有体系架构上
5 BFQ is a proportional-share I/O scheduler, with some extra25 As every I/O scheduler, BFQ adds some overhead to per-I/O-request38 process (already limited by the execution of the rest of the I/O91 - one or more virtual machines are performing I/O,228 performing random I/O that becomes mostly sequential if236 I/O.272 associated with I/O-bound applications performing sequential273 I/O: in fact, the longer these applications are served once278 perform sporadic and short I/O), because, the smaller the330 This parameter specifies how long BFQ should idle for next I/O[all …]
195 compose 'O' 'A' to '�'225 compose '`' 'O' to '�'227 compose '\'' 'O' to '�'229 compose '^' 'O' to '�'231 compose '~' 'O' to '�'233 compose '"' 'O' to '�'235 compose '/' 'O' to '�'
62 Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-67 Region 0: I/O ports at c150 [size=8]68 Region 1: I/O ports at c158 [size=8]78 0000:00:05.0: ttyS1 at I/O 0xc150 (irq = 10) is a 16550A79 0000:00:05.0: ttyS2 at I/O 0xc158 (irq = 10) is a 16550A
42 - The remaining entries setup the mapping for the standard I/O, memory and45 - 0x81000000: I/O memory region71 - "default": active state, puts PCIe I/O out of deep power down state72 - "idle": puts PCIe I/O into deep power down state86 - vdd-pex-supply: Power supply for digital PCIe I/O. Must supply 1.05 V.99 - vddio-pex-ctl-supply: Power supply for PCIe control I/O partition. Must117 - vddio-pex-ctl-supply: Power supply for PCIe control I/O partition. Must122 - hvddio-pex-supply: High-voltage supply for PCIe I/O and PCIe output125 - vddio-pex-ctl-supply: Power supply for PCIe control I/O partition. Must130 - dvdd-pex-supply: Power supply for digital PCIe I/O. Must supply 1.05 V.[all …]
14 Legacy I/O Interrupt Controller）、EIOINTC（Extended I/O Interrupt Controller）、153 - LIOINTC：即《龙芯3A5000处理器使用手册》第11.1节所描述的“传统I/O中断”；154 - EIOINTC：即《龙芯3A5000处理器使用手册》第11.2节所描述的“扩展I/O中断”；
58 volatile的存儲類型最初是爲那些內存映射的I/O寄存器而定義。在內核里，寄存器訪問也應59 該被鎖保護，但是人們也不希望編譯器「優化」臨界區內的寄存器訪問。內核里I/O的內存訪問60 是通過訪問函數完成的；不贊成通過指針對I/O內存的直接訪問，並且不是在所有體系架構上
116 ``make O=output/dir`` 选项可以为输出文件（包括 .config）指定备用位置。125 make O=/home/name/build/kernel menuconfig126 make O=/home/name/build/kernel127 sudo make O=/home/name/build/kernel modules_install install129 请注意：如果使用了 ``O=output/dir`` 选项，那么它必须用于make的所有调用。
14 provides I/O access to some legacy ISA devices.15 HiP06 is based on arm64 architecture where there is no I/O space. So, the16 I/O ports here are not CPU addresses, and there is no 'ranges' property in
24 - IVRS - AMD I/O Virtualization Reporting Structure25 - IVDB - AMD I/O Virtualization Definition Block26 - IVHD - AMD I/O Virtualization Hardware Definition41 The architecture defines an ACPI-compatible data structure called an I/O43 related to I/O virtualization to system software. The IVRS describes the50 - System I/O topology relevant to each IOMMU54 How is an I/O Virtual Address (IOVA) generated?
6 arbitrary mapping of fixed-size regions of I/O across a fixed set of10 It maps I/O to underlying block devices efficiently when there is a large28 stored on another member the I/O will be forwarded as required. This38 robin algorithm to send I/O across all paths and let the storage array51 Upper Tier - Determine which array member the I/O should be sent to.62 a bitmap to look up the location of the I/O and choose the appropriate63 lower tier device to route the I/O. By using a bitmap we are able to73 The number of paths across which to distribute the I/O.
3 tristate "Userspace I/O drivers"29 tristate "Userspace I/O platform driver with generic IRQ handling"31 Platform driver for Userspace I/O devices, including generic45 Platform driver for Userspace I/O devices, including generic66 This device differs from other UIO devices since it uses I/O67 ports instead of memory mapped I/O. In order to make it79 Userspace I/O interface for the Sercos III PCI card from150 Userspace I/O interface for the Humusoft MF624 PCI card.173 Generic DFL (Device Feature List) driver for Userspace I/O devices.
83 ${vpd_records}= Vpdtool -o -O ${component}85 # Example output from 'Vpdtool -o -O /system/chassis/motherboard/vdd_vrm1':131 ${vpd_records}= Vpdtool -o -O ${component}137 ${vpd_records}= Vpdtool -r -O ${component} -R VINI -K ${field}166 ${vpd_records}= Vpdtool -r -O ${component} -R VINI -K ${field}174 Vpdtool -w -O ${component} -R VINI -K ${field} --value ${write_value}187 Vpdtool -w -O ${component} -R VINI -K ${field} --value ${value}197 ${vpd_records}= Vpdtool -r -O ${component} -R VINI -K ${field}223 ${vpd_records}= Vpdtool -o -O ${component_url}