Searched +full:queue +full:- +full:sizes (Results 1 – 25 of 38) sorted by relevance
12
| /Documentation/devicetree/bindings/dma/ |
| D | fsl-qdma.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/dma/fsl-qdma.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Frank Li <Frank.Li@nxp.com>
15 - const: fsl,ls1021a-qdma
16 - items:
17 - enum:
18 - fsl,ls1028a-qdma
19 - fsl,ls1043a-qdma
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | userp.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
21 data are exchanged, these pointers and meta-information are passed in
23 :c:type:`v4l2_plane` in the multi-planar API case). The
33 .. code-block:: c
41 if (ioctl (fd, VIDIOC_REQBUFS, &reqbuf) == -1) {
50 Buffer (plane) addresses and sizes are passed on the fly with the
52 cycled, applications can pass different addresses and sizes at each
74 application waits until a filled buffer can be dequeued, and re-enqueues
81 <VIDIOC_QBUF>` blocks when no buffer is in the outgoing queue. When the
85 <func-select>` or :c:func:`poll()` function are always
[all …]
|
| D | vidioc-create-bufs.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_CREATE_BUFS - Create buffers for Memory Mapped or User Pointer or DMA Buffer I/O
39 create buffers of different sizes.
53 ``type`` field the requested buffer size (for single-planar) or plane
54 sizes (for multi-planar formats) will be used for the allocated buffers.
63 it is larger, then the value will be used as-is. In other words, the
77 .. flat-table:: struct v4l2_create_buffers
78 :header-rows: 0
79 :stub-columns: 0
82 * - __u32
[all …]
|
| D | buffer.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
11 the Streaming I/O methods. In the multi-planar API, the data is held in
14 copied. These pointers, together with meta-information like timestamps
18 :ref:`VIDIOC_DQBUF <VIDIOC_QBUF>` ioctl. In the multi-planar API,
19 some plane-specific members of struct :c:type:`v4l2_buffer`,
20 such as pointers and sizes for each plane, are stored in
27 ``V4L2_BUF_FLAG_TSTAMP_SRC_MASK`` in :ref:`buffer-flags`. These flags
33 mem-to-mem devices is an exception to the rule: the timestamp source
112 or control set ioctl to return the ``EBUSY`` error. Any attempt to queue a
133 currently queued, without checking the queued buffers sizes.
[all …]
|
| D | diff-v4l.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 .. _diff-v4l:
23 and below in :ref:`v4l-dev`.
25 The teletext devices (minor range 192-223) have been removed in V4L2 and
35 .. _v4l-dev:
37 .. flat-table:: V4L Device Types, Names and Numbers
38 :header-rows: 1
39 :stub-columns: 0
41 * - Device Type
42 - File Name
[all …]
|
| /Documentation/admin-guide/mm/ |
| D | transhuge.rst | 12 that supports the automatic promotion and demotion of page sizes and
26 requiring larger clear-page copy-page in page faults which is a
48 Modern kernels support "multi-size THP" (mTHP), which introduces the
50 but smaller than traditional PMD-size (as described above), in
51 increments of a power-of-2 number of pages. mTHP can back anonymous
53 PTE-mapped, but in many cases can still provide similar benefits to
56 prominent because the size of each page isn't as huge as the PMD-sized
66 collapses sequences of basic pages into PMD-sized huge pages.
91 possible to disable hugepages system-wide and to only have them inside
108 -------------------
[all …]
|
| /Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 1 .. SPDX-License-Identifier: GPL-2.0
29 "full" and "not-in-use". An "empty" or "ready" descriptor is ready
31 and is waiting to be emptied and processed by the OS. A "not-in-use"
40 buffers, processing them, and re-marking them empty.
54 descr. The OS will process this descr, and then mark it "not-in-use",
57 all of those behind it should be "not-in-use". When RX traffic is not
62 The head pointer (somewhat mis-named) follows after the tail pointer.
64 a "not-in-use" descr. The OS will perform various housekeeping duties
66 dma-mapping it so as to make it visible to the hardware. The OS will
69 be "not-in-use", and everything behind it should be "empty". If no
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-block | 7 with 4KB physical sectors exposing 512-byte logical
35 power-of-two and atomic_write_unit_max_bytes may also be
36 limited by some other queue limits, such as max_segments.
37 This parameter - along with atomic_write_unit_min_bytes
38 and atomic_write_unit_max_bytes - will not be larger than
50 atomic_write_unit_min. This value must be a power-of-two.
60 be a power-of-two. This value will not be larger than
72 power-of-two and at least the size as in
96 than the number of requests queued in the block device queue.
102 This is related to /sys/block/<disk>/queue/nr_requests
[all …]
|
| /Documentation/arch/sparc/oradax/ |
| D | dax-hv-api.txt | 3 Publication date 2017-09-25 08:21
5 Extracted via "pdftotext -f 547 -l 572 -layout sun4v_20170925.pdf"
16 live-migration and other system management activities.
20 …high speed processoring of database-centric operations. The coprocessors may support one or more of
28 …e Completion Area and, unless execution order is specifically restricted through the use of serial-
36 …killing it in order to determine if the CCB is still in queue, or may have been lost due to a RAS …
45 …device node in the guest MD (Section 8.24.17, “Database Analytics Accelerators (DAX) virtual-device
51 36.1.1.1. "ORCL,sun4v-dax" Device Compatibility
54 • No-op/Sync
81 36.1.1.2. "ORCL,sun4v-dax-fc" Device Compatibility
[all …]
|
| /Documentation/driver-api/rapidio/ |
| D | tsi721.rst | 2 RapidIO subsystem mport driver for IDT Tsi721 PCI Express-to-SRIO bridge.
10 doorbells, inbound maintenance port-writes and RapidIO messaging.
18 into the corresponding message queue. Messaging callbacks are implemented to be
23 - 'dbg_level'
24 - This parameter allows to control amount of debug information
32 - 'dma_desc_per_channel'
33 - This parameter defines number of hardware buffer
37 - 'dma_txqueue_sz'
38 - DMA transactions queue size. Defines number of pending
42 - 'dma_sel'
[all …]
|
| /Documentation/locking/ |
| D | mutex-design.rst | 10 -----------------
24 --------------
28 (->owner) to keep track of the lock state during its lifetime. Field owner
32 if waiter list is non-empty). In its most basic form it also includes a
33 wait-queue and a spinlock that serializes access to it. Furthermore,
34 CONFIG_MUTEX_SPIN_ON_OWNER=y systems use a spinner MCS lock (->osq), described
52 The MCS lock (proposed by Mellor-Crummey and Scott) is a simple spinlock
55 cacheline bouncing that common test-and-set spinlock implementations
56 incur. An MCS-like lock is specially tailored for optimistic spinning
59 the MCS spinlock queue when they need to reschedule. This further helps
[all …]
|
| /Documentation/networking/devlink/ |
| D | mlx5.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 .. list-table:: Generic parameters implemented
15 * - Name
16 - Mode
17 - Validation
18 * - ``enable_roce``
19 - driverinit
20 - Type: Boolean
26 * - ``io_eq_size``
27 - driverinit
[all …]
|
| /Documentation/block/ |
| D | bfq-iosched.rst | 5 BFQ is a proportional-share I/O scheduler, with some extra
6 low-latency capabilities. In addition to cgroups support (blkio or io
9 - BFQ guarantees a high system and application responsiveness, and a
10 low latency for time-sensitive applications, such as audio or video
12 - BFQ distributes bandwidth, not just time, among processes or
19 goal, for a given device, is to achieve the maximum-possible
20 throughput at all times, then do switch off all low-latency heuristics
25 As every I/O scheduler, BFQ adds some overhead to per-I/O-request
27 single-lock-protected, per-request processing time of BFQ---i.e., the
29 completion hooks---is, e.g., 1.9 us on an Intel Core i7-2760QM@2.40GHz
[all …]
|
| /Documentation/usb/ |
| D | ehci.rst | 5 27-Dec-2002
8 USB 2.0-capable host controller hardware. The USB 2.0 standard is
11 - "High Speed" 480 Mbit/sec (60 MByte/sec)
12 - "Full Speed" 12 Mbit/sec (1.5 MByte/sec)
13 - "Low Speed" 1.5 Mbit/sec
31 While usb-storage devices have been available since mid-2001 (working
34 appear to be on hold until more systems come with USB 2.0 built-in.
39 other changes to the Linux-USB core APIs, including the hub driver,
43 - David Brownell
56 --------------
[all …]
|
| D | gadget_uvc.rst | 6 --------
8 connection. It is intended to run on a Linux system that has USB device-side
18 queue image buffers from a variety of sources to be transmitted via the USB
24 -----------------------------
29 ---------------------------------------
35 see Documentation/ABI/testing/configfs-usb-gadget-uvc
47 .. code-block:: bash
54 mkdir -p $FUNCTION
60 as the frame sizes and frame intervals that are supported for each format. In
99 .. code-block:: bash
[all …]
|
| /Documentation/devicetree/bindings/crypto/ |
| D | fsl,sec-v4.0.yaml | 1 # SPDX-License-Identifier: GPL-2.0
2 # Copyright (C) 2008-2011 Freescale Semiconductor Inc.
4 ---
5 $id: http://devicetree.org/schemas/crypto/fsl,sec-v4.0.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - '"Horia Geantă" <horia.geanta@nxp.com>'
12 - Pankaj Gupta <pankaj.gupta@nxp.com>
13 - Gaurav Jain <gaurav.jain@nxp.com>
20 1. DPAA Queue Interface (HW interface between Queue Manager & SEC 4).
25 HW interface between QM & SEC 4 and also BM & SEC 4, on DPAA-enabled parts
[all …]
|
| /Documentation/spi/ |
| D | spi-summary.rst | 5 02-Feb-2012
8 ------------
17 clocking modes through which data is exchanged; mode-0 and mode-3 are most
32 - SPI may be used for request/response style device protocols, as with
35 - It may also be used to stream data in either direction (half duplex),
38 - Some devices may use eight bit words. Others may use different word
39 lengths, such as streams of 12-bit or 20-bit digital samples.
41 - Words are usually sent with their most significant bit (MSB) first,
44 - Sometimes SPI is used to daisy-chain devices, like shift registers.
51 SPI is only one of the names used by such four-wire protocols, and
[all …]
|
| /Documentation/networking/device_drivers/ethernet/intel/ |
| D | i40e.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
8 Copyright(c) 1999-2018 Intel Corporation.
13 - Overview
14 - Identifying Your Adapter
15 - Intel(R) Ethernet Flow Director
16 - Additional Configurations
17 - Known Issues
18 - Support
47 ----------------------
49 …intel.com/content/dam/www/public/us/en/documents/release-notes/xl710-ethernet-controller-feature-m…
[all …]
|
| D | ice.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
8 Copyright(c) 2018-2021 Intel Corporation.
13 - Overview
14 - Identifying Your Adapter
15 - Important Notes
16 - Additional Features & Configurations
17 - Performance Optimization
28 This driver supports XDP (Express Data Path) and AF_XDP zero-copy. Note that
29 XDP is blocked for frame sizes larger than 3KB.
43 -------------------------------------------
[all …]
|
| /Documentation/networking/device_drivers/can/ctu/ |
| D | ctucanfd-driver.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later
10 ------------------------
19 `Vivado integration <https://gitlab.fel.cvut.cz/canbus/zynq/zynq-can-sja1000-top>`_
20 and Intel Cyclone V 5CSEMA4U23C6 based DE0-Nano-SoC Terasic board
21 `QSys integration <https://gitlab.fel.cvut.cz/canbus/intel-soc-ctucanfd>`_
23 `PCIe integration <https://gitlab.fel.cvut.cz/canbus/pcie-ctucanfd>`_ of the core.
33 version of emulation support can be cloned from ctu-canfd branch of QEMU local
34 development `repository <https://gitlab.fel.cvut.cz/canbus/qemu-canbus>`_.
38 ---------------
59 it allows for device hot-plug.
[all …]
|
| /Documentation/bpf/ |
| D | ringbuf.rst | 12 ----------
18 - more efficient memory utilization by sharing ring buffer across CPUs;
19 - preserving ordering of events that happen sequentially in time, even across
23 Both are a result of a choice to have per-CPU perf ring buffer. Both can be
25 problem could technically be solved for perf buffer with some in-kernel
30 ------------------
54 types (e.g., queue and stack; array doesn't support delete, etc).
56 The approach chosen has an advantage of re-using existing BPF map
62 combined with ``ARRAY_OF_MAPS`` and ``HASH_OF_MAPS`` map-in-maps to implement
69 Key and value sizes are enforced to be zero. ``max_entries`` is used to specify
[all …]
|
| /Documentation/networking/ |
| D | lapb-module.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 Changed (Henner Eisen, 2000-10-29): int return value for data_indication()
25 ----------
37 -----------------------------
59 ------------------------
93 3-31 Reserved, must be 0.
97 consequently larger window sizes, the default is standard LAPB operation.
107 ---------
202 Queue data with the LAPB module for transmitting over the link. If the call
216 Queue data with the LAPB module which has been received from the device. It
[all …]
|
| /Documentation/core-api/ |
| D | swiotlb.rst | 1 .. SPDX-License-Identifier: GPL-2.0
19 These APIs use the device DMA attributes and kernel-wide settings to determine
30 ---------------
32 limitations. As physical memory sizes grew beyond 4 GiB, some devices could
33 only provide 32-bit DMA addresses. By allocating bounce buffer memory below
40 directed to guest memory that is unencrypted. CoCo VMs set a kernel-wide option
54 IOMMU access control is per-granule, the untrusted device can gain access to
60 ------------------
85 ------------------------------
89 pre-allocated at boot time (but see Dynamic swiotlb below). Because swiotlb
[all …]
|
| /Documentation/networking/device_drivers/ethernet/stmicro/ |
| D | stmmac.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
13 - In This Release
14 - Feature List
15 - Kernel Configuration
16 - Command Line Parameters
17 - Driver Information and Notes
18 - Debug Information
19 - Support
33 (and older) and DesignWare(R) Cores Ethernet Quality-of-Service version 4.0
35 DesignWare(R) Cores XGMAC - 10G Ethernet MAC and DesignWare(R) Cores
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | vdo-design.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
4 Design of dm-vdo
7 The dm-vdo (virtual data optimizer) target provides inline deduplication,
8 compression, zero-block elimination, and thin provisioning. A dm-vdo target
12 production environments ever since. It was made open-source in 2017 after
14 dm-vdo. For usage, see vdo.rst in the same directory as this file.
25 The design of dm-vdo is based on the idea that deduplication is a two-part
27 storing multiple copies of those duplicates. Therefore, dm-vdo has two main
34 -------------------
39 block sizes in order to achieve good deduplication rates, acceptable
[all …]
|
12