| /Documentation/devicetree/bindings/net/wireless/ |
| D | qcom,ath11k.yaml | 109 - description: interrupt event for ring CE0
110 - description: interrupt event for ring CE1
111 - description: interrupt event for ring CE2
112 - description: interrupt event for ring CE3
113 - description: interrupt event for ring CE4
114 - description: interrupt event for ring CE5
115 - description: interrupt event for ring CE6
116 - description: interrupt event for ring CE7
117 - description: interrupt event for ring CE8
118 - description: interrupt event for ring CE9
[all …]
|
| /Documentation/userspace-api/ |
| D | perf_ring_buffer.rst | 4 Perf ring buffer
11 2. Ring buffer implementation
13 2.2 Ring buffer for different tracing modes
20 2.3.2 Properties of the ring buffers
25 3. The mechanism of AUX ring buffer
26 3.1 The relationship between AUX and regular ring buffers
34 The ring buffer is a fundamental mechanism for data transfer. perf uses
35 ring buffers to transfer event data from kernel to user space, another
36 kind of ring buffer which is so called auxiliary (AUX) ring buffer also
40 The ring buffer implementation is critical but it's also a very
[all …]
|
| D | vduse.rst | 141 avail index for split virtqueue or the device/driver ring wrap counters and
158 including the size, the IOVAs of descriptor table, available ring and used ring,
223 consume the available ring. This is optional since userspace can choose to poll the
224 available ring instead.
226 4. Listen to the kick eventfd (optional) and consume the available ring. The buffer
231 after the used ring is filled.
|
| /Documentation/mhi/ |
| D | mhi.rst | 85 transfer ring.
93 memory. TDs consist of one or more ring elements (or transfer blocks)::
95 [Read Pointer (RP)] ----------->[Ring Element] } TD
96 [Write Pointer (WP)]- [Ring Element]
97 - [Ring Element]
98 --------->[Ring Element]
99 [Ring Element]
103 * Host allocates memory for transfer ring.
106 * Ring is considered empty when RP == WP.
107 * Ring is considered full when WP + 1 == RP.
[all …]
|
| /Documentation/bpf/ |
| D | ringbuf.rst | 2 BPF ring buffer
5 This document describes BPF ring buffer design, API, and implementation details.
15 existing perf buffer, which prompted creation of a new ring buffer
18 - more efficient memory utilization by sharing ring buffer across CPUs;
23 Both are a result of a choice to have per-CPU perf ring buffer. Both can be
24 also solved by having an MPSC implementation of ring buffer. The ordering
32 Single ring buffer is presented to BPF programs as an instance of BPF map of
37 ``BPF_MAP_TYPE_RINGBUF`` could represent an array of ring buffers, but not
40 advanced logic to lookup ring buffer by arbitrary key.
43 opt into a simple single ring buffer shared among all CPUs, for which current
[all …]
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | raideng.txt | 48 There must be a sub-node for each job ring present in RAID Engine
51 - compatible: Must contain "fsl,raideng-v1.0-job-ring" as the value
52 This identifies job ring. Should contain either
53 "fsl,raideng-v1.0-hp-ring" or "fsl,raideng-v1.0-lp-ring"
54 depending upon whether ring has high or low priority
55 - reg: offset and length of the register set for job ring
56 - interrupts: interrupt mapping for job ring IRQ
60 - fsl,liodn: Specifies the LIODN to be used for Job Ring. This
75 compatible = "fsl,raideng-v1.0-job-ring", "fsl,raideng-v1.0-hp-ring";
|
| /Documentation/networking/ |
| D | af_xdp.rst | 24 syscall. Associated with each XSK are two rings: the RX ring and the
25 TX ring. A socket can receive packets on the RX ring and it can send
26 packets on the TX ring. These rings are registered and sized with the
29 descriptor ring points to a data buffer in a memory area called a
42 UMEM also has two rings: the FILL ring and the COMPLETION ring. The
43 FILL ring is used by the application to send down addr for the kernel
45 appear in the RX ring once each packet has been received. The
46 COMPLETION ring, on the other hand, contains frame addr that the
49 COMPLETION ring are addrs that were previously transmitted using the
50 TX ring. In summary, the RX and FILL rings are used for the RX path
[all …]
|
| D | packet_mmap.rst | 68 setsockopt() ---> allocation of the circular buffer (ring)
96 allocated RX and TX buffer ring with a single mmap() call.
97 See "Mapping and use of the circular buffer (ring)".
108 setsockopt() ---> allocation of the circular buffer (ring)
116 the ring
212 circular buffer (ring) of unswappable memory.
249 buffer (ring)".
403 Mapping and use of the circular buffer (ring)
420 RX and TX buffer ring has to be done with one call to mmap::
429 RX must be the first as the kernel maps the TX ring memory right
[all …]
|
| /Documentation/trace/ |
| D | ring-buffer-map.rst | 4 Tracefs ring-buffer memory mapping
11 Tracefs ring-buffer memory map provides an efficient method to stream data
12 as no memory copy is necessary. The application mapping the ring-buffer becomes
13 then a consumer for that ring-buffer, in a similar fashion to trace_pipe.
19 The first system page of the mapping contains ring-buffer statistics and
22 be safely read by the mapper (see ring-buffer-design.rst).
38 When a mapping is in place on a Tracefs ring-buffer, it is not possible to
39 either resize it (either by increasing the entire size of the ring-buffer or
41 the ring buffer data instead of using the copyless swap from the ring buffer.
43 Concurrent readers (either another application mapping that ring-buffer or the
[all …]
|
| D | debugging.rst | 30 written to the tracing ring buffer in a lockless way. To make it even
33 arguments will be post processed when the ring buffer is read. This way the
62 The tracing ring buffer, by default, is a circular buffer than will
64 the ring buffer will be all the events that lead up to the crash.
67 this. The first is "ftrace_dump_on_oops". This will dump the tracing ring
70 make sure the ring buffer is relatively small, otherwise the dumping of the
71 ring buffer may take several minutes to hours to finish. Here's an example
83 If the system memory allows it, the tracing ring buffer can be specified at
86 following boot. There's two ways to reserve memory for the use of the ring
92 advantage of using this method, is that the memory for the ring buffer will
[all …]
|
| D | index.rst | 31 ring-buffer-design
32 ring-buffer-map
|
| D | ring-buffer-design.rst | 4 Lockless Ring Buffer Design
22 - where new writes happen in the ring buffer.
25 - where new reads happen in the ring buffer.
28 - the task that writes into the ring buffer (same as writer)
40 - A page outside the ring buffer used solely (for the most part)
66 The Generic Ring Buffer
69 The ring buffer can be used in either an overwrite mode or in
108 The ring buffer is made up of a list of pages held together by a linked list.
111 part of the ring buffer.
124 become part of the ring buffer and the head_page will be removed.
[all …]
|
| /Documentation/devicetree/bindings/crypto/ |
| D | fsl-sec6.txt | 5 -Job Ring Node
72 Job Ring (JR) Node
84 Definition: Must include "fsl,sec-v6.0-job-ring".
103 compatible = "fsl,sec-v6.0-job-ring";
123 compatible = "fsl,sec-v6.0-job-ring",
124 "fsl,sec-v5.2-job-ring",
125 "fsl,sec-v5.0-job-ring",
126 "fsl,sec-v4.4-job-ring",
127 "fsl,sec-v4.0-job-ring";
132 compatible = "fsl,sec-v6.0-job-ring",
[all …]
|
| D | fsl,sec-v4.0.yaml | 31 Job Ring Data Path Configuration:
87 Job Ring (JR) Node. Defines data processing interface to SEC 4 across the
97 - const: fsl,sec-v5.4-job-ring
98 - const: fsl,sec-v5.0-job-ring
99 - const: fsl,sec-v4.0-job-ring
101 - const: fsl,sec-v5.0-job-ring
102 - const: fsl,sec-v4.0-job-ring
103 - const: fsl,sec-v4.0-job-ring
218 compatible = "fsl,sec-v4.0-job-ring";
224 compatible = "fsl,sec-v4.0-job-ring";
[all …]
|
| /Documentation/devicetree/bindings/soc/ti/ |
| D | k3-ringacc.yaml | 8 title: Texas Instruments K3 NavigatorSS Ring Accelerator
15 The Ring Accelerator (RA) is a machine which converts read/write accesses
18 controller which needs to access ring elements from having to know the current
19 state of the ring (base address, current offset). The DMA controller
22 with a new address which corresponds to the head or tail element of the ring
25 The Ring Accelerator is a hardware module that is responsible for accelerating
62 description: TI-SCI RM subtype for GP ring range
91 ti,sci-rm-range-gp-rings = <0x2>; /* GP ring range */
|
| /Documentation/virt/hyperv/ |
| D | vmbus.rst | 60 Each channel consists of two ring buffers. These are classic ring
62 and writes pointers are equal, the ring buffer is considered to be
63 empty, so a full ring buffer always has at least one byte unused.
64 The "in" ring buffer is for messages from the Hyper-V host to the
65 guest, and the "out" ring buffer is for messages from the guest to
67 viewed by the guest side. The ring buffers are memory that is
70 of GPAs that make up the ring buffer communicated to the host. Each
71 ring buffer consists of a header page (4 Kbytes) with the read and
73 actual ring. The size of the ring is determined by the VSC in the
75 making up the ring is communicated to the Hyper-V host over the
[all …]
|
| /Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 18 The Structure of the RX Ring.
20 The receive (RX) ring is a circular linked list of RX descriptors,
21 together with three pointers into the ring that are used to manage its
24 The elements of the ring are called "descriptors" or "descrs"; they
38 ring is handed off to the hardware, which sequentially fills in the
76 other descrs in the ring should be "empty" as well.
80 of the ring, starting at the tail pointer, and listing the status
118 the OS fails to empty the RX ring fast enough, the hardware GDACTDPA
128 When the OS finally has a chance to run, it will empty out the RX ring.
176 search the ring for the next full descr, and the driver will resume
[all …]
|
| /Documentation/arch/x86/x86_64/ |
| D | fred.rst | 11 privilege level (ring transitions). The FRED architecture was
25 FRED event delivery can effect a transition from ring 3 to ring 0, but
26 it is used also to deliver events incident to ring 0. One FRED
27 instruction (ERETU) effects a return from ring 0 to ring 3, while the
28 other (ERETS) returns while remaining in ring 0. Collectively, FRED
77 Because FRED event delivery from ring 3 and ERETU both swap the value
|
| /Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| D | counters.rst | 67 Ring
71 An aggregation of software ring counters.
123 Ring / Netdev Counter
125 The following counters are available per ring or software port.
131 The counter names in the table below refers to both ring and port counters. The
132 notation for ring counters includes the [i] index without the braces. The
134 `rx[i]_packets` will be printed as `rx0_packets` for ring 0 and `rx_packets` for
137 .. flat-table:: Ring / Software Port Counter Table
145 - The number of packets received on ring i.
149 - The number of bytes received on ring i.
[all …]
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | brcm,iproc-flexrm-mbox.txt | 1 Broadcom FlexRM Ring Manager
3 The Broadcom FlexRM ring manager provides a set of rings which can be
7 hardware block where each mailbox channel is a separate FlexRM ring.
13 ring registers
16 interrupts) to CPU. There is one MSI for each FlexRM ring.
|
| /Documentation/target/ |
| D | tcmu-design.rst | 14 ii. Command ring
22 c) Managing the command ring
117 the ring to still work if the user process dies and is restarted with
127 command ring, and head and tail pointers to be used by the kernel and
128 userspace (respectively) to put commands on the ring, and indicate
136 See "The Command Ring" for details.
139 The offset of the start of the command ring from the start
142 The size of the command ring. This does *not* need to be a
146 placed on the ring.
151 The Command Ring
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | cirrus,cs42l43.yaml | 145 cirrus,use-ring-sense:
148 Indicates if the ring sense should be used.
150 cirrus,ring-invert:
153 Indicates ring detect polarity, inverted implies open-circuit whilst the
156 cirrus,ring-disable-pullup:
159 Indicates if the internal pullup on the ring detect should be disabled.
161 cirrus,ring-fall-db-ms:
163 Time in milliseconds a falling edge on the ring detect should be hardware
168 cirrus,ring-rise-db-ms:
170 Time in milliseconds a rising edge on the ring detect should be hardware
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-qat_rl | 41 (RW) When read, reports the current assigned ring pairs for the
43 When wrote to, configures the ring pairs associated to a new SLA.
46 Each bit of this mask represents a single ring pair i.e.,
47 bit 1 == ring pair id 0; bit 3 == ring pair id 2.
49 Selected ring pairs must to be assigned to a single service,
51 assigned to a certain ring pair can be checked by querying
54 The maximum number of ring pairs is 4 per SLA.
102 0x5 ## ring pair ID 0 and ring pair ID 2
|
| D | sysfs-driver-qat | 105 specific ring pair for the type of service that it is currently
110 N is the max number of ring pairs supported by a device. This
113 A read returns the service associated to the ring pair queried.
117 * dc: the ring pair is configured for running compression services
118 * sym: the ring pair is configured for running symmetric crypto
120 * asym: the ring pair is configured for running asymmetric crypto
136 (RO) Returns the number of ring pairs that a single device has.
|
| /Documentation/networking/device_drivers/fddi/ |
| D | defza.rst | 23 existing IEEE 802.3 10BASE2 Ethernet and IEEE 802.5 Token Ring networks
35 Two entries are preoccupied by the Directed Beacon and Ring Purger
56 receive/RMC transmit ring is full. (?)
|