Searched +full:side +full:- +full:by +full:- +full:side (Results 1 – 25 of 1052) sorted by relevance
12345678910>>...43
| /linux-6.14.4/tools/perf/pmu-events/arch/x86/silvermont/ |
| D | virtual-memory.json | 13 "BriefDescription": "Total cycles for all the page walks. (I-side and D-side)",
22 "BriefDescription": "Duration of D-side page-walks in core cycles",
26 …when a D-side (walks due to a load) page walk is in progress. Page walk duration divided by number…
31 "BriefDescription": "D-side page-walks",
36 …ce a page walk implies a TLB miss, the number of TLB misses can be counted by counting the number …
41 "BriefDescription": "Duration of I-side page-walks in core cycles",
45 …I-side (walks due to an instruction fetch) page walk is in progress. Page walk duration divided by…
50 "BriefDescription": "I-side page-walks",
55 …ce a page walk implies a TLB miss, the number of TLB misses can be counted by counting the number …
60 "BriefDescription": "Total page walks that are completed (I-side and D-side)",
[all …]
|
| /linux-6.14.4/Documentation/RCU/ |
| D | checklist.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 0. Is RCU being applied to a read-mostly situation? If the data
18 tool for the job. Yes, RCU does reduce read-side overhead by
19 increasing write-side overhead, which is exactly why normal uses
27 Yet another exception is where the low real-time latency of RCU's
28 read-side primitives is critically important.
33 counter-intuitive situation where rcu_read_lock() and
49 them -- even x86 allows later loads to be reordered to precede
54 relating to itself that other tasks can read, there by definition
59 2. Do the RCU read-side critical sections make proper use of
[all …]
|
| D | lockdep.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 aware of when each task enters and leaves any flavor of RCU read-side
18 rcu_read_lock_bh_held() for RCU-bh.
19 rcu_read_lock_sched_held() for RCU-sched.
20 rcu_read_lock_any_held() for any of normal RCU, RCU-bh, and RCU-sched.
33 Check for RCU read-side critical section.
35 Check for RCU-bh read-side critical section.
37 Check for RCU-sched read-side critical section.
39 Check for SRCU read-side critical section.
43 invoked by both RCU readers and updaters.
[all …]
|
| D | whatisRCU.rst | 3 What is RCU? -- "Read, Copy, Update"
21 …ries: Fundamentals https://www.linuxfoundation.org/webinars/unraveling-rcu-usage-mysteries
22 …Cases https://www.linuxfoundation.org/webinars/unraveling-rcu-usage-mysteries-additional-use-cases
28 during the 2.5 development effort that is optimized for read-mostly
47 :ref:`6. ANALOGY WITH READER-WRITER LOCKING <6_whatisRCU>`
56 Section 1, though most readers will profit by reading this section at
61 into the kernel source code. People who reason best by analogy should
67 everything, feel free to read the whole thing -- but if you are really
69 never need this document anyway. ;-)
74 ----------------
[all …]
|
| /linux-6.14.4/Documentation/locking/ |
| D | seqlock.rst | 8 Sequence counters are a reader-writer consistency mechanism with
9 lockless readers (read-only retry loops), and no writer starvation. They
15 read side critical section is even and the same sequence count value is
17 be copied out inside the read side critical section. If the sequence
24 the end of the write side critical section the sequence count becomes
27 A sequence counter write side critical section must never be preempted
28 or interrupted by read side sections. Otherwise the reader will spin for
30 interrupted writer. If that reader belongs to a real-time scheduling
43 multiple writers. Write side critical sections must thus be serialized
44 by an external lock.
[all …]
|
| /linux-6.14.4/Documentation/devicetree/bindings/interrupt-controller/ |
| D | fsl,mu-msi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/interrupt-controller/fsl,mu-msi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Frank Li <[email protected]>
14 communicate and coordinate by passing messages (e.g. data, status
16 for one processor (A side) to signal the other processor (B side) using
20 different clocks (from each side of the different peripheral buses).
21 Therefore, the MU must synchronize the accesses from one side to the
23 registers (Processor A-side, Processor B-side).
[all …]
|
| /linux-6.14.4/tools/perf/pmu-events/arch/arm64/ampere/ampereone/ |
| D | core-imp-def.json | 99 "PublicDescription": "Macro-ops speculatively decoded",
102 "BriefDescription": "Macro-ops speculatively decoded"
249 "PublicDescription": "Number of SWOB drains triggered by timeout",
252 "BriefDescription": "Number of SWOB drains triggered by timeout"
255 … "Number of SWOB drains triggered by system register or special-purpose register read-after-write …
258 … "Number of SWOB drains triggered by system register or special-purpose register read-after-write …
261 … "PublicDescription": "Number of SWOB drains triggered by system register write when SWOB full",
264 … "BriefDescription": "Number of SWOB drains triggered by system register write when SWOB full"
297 "PublicDescription": "Instructions issued by the scheduler",
300 "BriefDescription": "Instructions issued by the scheduler"
[all …]
|
| /linux-6.14.4/Documentation/usb/ |
| D | gadget_serial.rst | 7 (updated 8-May-2008 for v2.3)
11 ----------------------
14 published by the Free Software Foundation; either version 2 of
25 MA 02111-1307 USA.
28 Copyright (C) 2004 by Al Borchers ([email protected]).
35 -------------
55 --------
57 side driver. It runs on a Linux system that has USB device side
65 --------------------------------------
66 | Host-Side CDC ACM USB Host |
[all …]
|
| /linux-6.14.4/Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 16 ------------
18 Read-copy update (RCU) is a synchronization mechanism that is often used
19 as a replacement for reader-writer locking. RCU is unusual in that
20 updaters do not block readers, which means that RCU's read-side
28 thought of as an informal, high-level specification for RCU. It is
40 #. `Fundamental Non-Requirements`_
42 #. `Quality-of-Implementation Requirements`_
44 #. `Software-Engineering Requirements`_
48 This is followed by a summary_, however, the answers to
53 ------------------------
[all …]
|
| /linux-6.14.4/tools/perf/pmu-events/arch/x86/ivytown/ |
| D | uncore-cache.json | 15 …ted information by filtering the Cb0 occupancy count captured in Counter 0. The filtering availa…
24 … LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has numer…
34 … LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has numer…
44 …- this includes code, data, prefetches and hints coming from L2. This has numerous filters availa…
54 … LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has numer…
64 …- this includes code, data, prefetches and hints coming from L2. This has numerous filters availa…
74 … the number of lines that were victimized on a fill. This can be filtered by the state that the l…
84 … the number of lines that were victimized on a fill. This can be filtered by the state that the l…
94 … the number of lines that were victimized on a fill. This can be filtered by the state that the l…
104 …imized on a fill. This can be filtered by the state that the line was in.; Qualify one of the oth…
[all …]
|
| /linux-6.14.4/drivers/block/rnbd/ |
| D | README | 6 ------------
12 on the client side as local block devices.
14 I/O is transferred between client and server by the RTRS transport
19 ------------
24 -----------
26 Server side:
29 Client side:
32 /sys/devices/virtual/rnbd-client/ctl/map_device
36 a pair of a source and a destination IPs, separated by comma. Multiple
39 mapped from the server side. After the session to the server machine is
[all …]
|
| /linux-6.14.4/drivers/char/hw_random/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
13 module will be called rng-core. This provides a device
28 This driver provides kernel-side support for a generic Random
29 Number Generator used by reading a 'dumb' iomem address that
31 the default FPGA bitstream on the TS-7800 has such functionality.
34 module will be called timeriomem-rng.
43 This driver provides kernel-side support for the Random Number
44 Generator hardware found on Intel i8xx-based motherboards.
47 module will be called intel-rng.
57 This driver provides kernel-side support for the Random Number
[all …]
|
| /linux-6.14.4/include/linux/ |
| D | srcu.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
3 * Sleepable Read-Copy Update mechanism for mutual exclusion
11 * For detailed explanation of Read-Copy Update mechanism see -
46 /* Values for SRCU Tree srcu_data ->srcu_reader_flavor, but also used by rcutorture. */
77 * get_completed_synchronize_srcu - Return a pre-completed polled state cookie
92 // not-yet-completed SRCU grace periods.
96 * same_state_synchronize_srcu - Are two old-state values identical?
97 * @oldstate1: First old-state value.
98 * @oldstate2: Second old-state value.
100 * The two old-state values must have been obtained from either
[all …]
|
| D | rcupdate.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
3 * Read-Copy Update mechanism for mutual exclusion
9 * Based on the original work by Paul McKenney <[email protected]>
15 * For detailed explanation of Read-Copy Update mechanism see -
34 #define ULONG_CMP_GE(a, b) (ULONG_MAX / 2 >= (a) - (b))
35 #define ULONG_CMP_LT(a, b) (ULONG_MAX / 2 < (a) - (b))
38 #define RCU_SEQ_STATE_MASK ((1 << RCU_SEQ_CTR_SHIFT) - 1)
50 // not-yet-completed RCU grace periods.
54 * same_state_synchronize_rcu - Are two old-state values identical?
55 * @oldstate1: First old-state value.
[all …]
|
| /linux-6.14.4/rust/kernel/sync/ |
| D | rcu.rs | 1 // SPDX-License-Identifier: GPL-2.0
9 /// Evidence that the RCU read side lock is held on the current thread/CPU.
11 /// The type is explicitly not `Send` because this property is per-thread/CPU.
15 /// The RCU read side lock is actually held while instances of this guard exist.
19 /// Acquires the RCU read side lock and returns a guard.
20 pub fn new() -> Self { in new()
23 // INVARIANT: The RCU read side lock was just acquired above. in new()
27 /// Explicitly releases the RCU read side lock.
32 fn default() -> Self { in default()
39 // SAFETY: By the type invariants, the RCU read side is locked, so it is ok to unlock it. in drop()
[all …]
|
| /linux-6.14.4/drivers/char/ipmi/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
7 tristate 'IPMI top-level message handler'
17 See <file:Documentation/driver-api/ipmi.rst> for more details on the driver.
34 by default, generate an IPMI event describing the panic to each
45 by default, generate IPMI OEM type f0 events holding the IPMB
91 Provides a driver for OPAL firmware-based IPMI interfaces.
118 The driver implements the BMC side of the KCS contorller, it
119 provides the access of KCS IO space for BMC side.
130 The driver implements the BMC side of the KCS contorller, it
131 provides the access of KCS IO space for BMC side.
[all …]
|
| /linux-6.14.4/drivers/media/platform/mediatek/vcodec/encoder/venc/ |
| D | venc_h264_if.c | 1 // SPDX-License-Identifier: GPL-2.0
27 * enum venc_h264_frame_type - h264 encoder output bitstream frame type
37 * enum venc_h264_vpu_work_buf - h264 encoder buffer index
53 * enum venc_h264_bs_mode - for bs_mode argument in h264_enc_vpu_encode
62 * struct venc_h264_vpu_config - Structure for h264 encoder configuration
63 * AP-W/R : AP is writer/reader on this item
64 * VPU-W/R: VPU is write/reader on this item
97 * struct venc_h264_vpu_buf - Structure for buffer information
98 * AP-W/R : AP is writer/reader on this item
99 * VPU-W/R: VPU is write/reader on this item
[all …]
|
| D | venc_vp8_if.c | 1 // SPDX-License-Identifier: GPL-2.0
27 * enum venc_vp8_vpu_work_buf - vp8 encoder buffer index
47 * struct venc_vp8_vpu_config - Structure for vp8 encoder configuration
48 * AP-W/R : AP is writer/reader on this item
49 * VPU-W/R: VPU is write/reader on this item
62 * support three temporal layers - 0: 7.5fps 1: 7.5fps 2: 15fps.
77 * struct venc_vp8_vpu_buf - Structure for buffer information
78 * AP-W/R : AP is writer/reader on this item
79 * VPU-W/R: VPU is write/reader on this item
81 * @vpua: VPU side memory addr which is used by RC_CODE
[all …]
|
| /linux-6.14.4/sound/pci/hda/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "HD-Audio"
23 This option enables the HD-audio controller. Don't forget
27 will be called snd-hda-intel.
43 will be called snd-hda-tegra.
48 bool "Build hwdep interface for HD-audio driver"
51 Say Y here to build a hwdep interface for HD-audio driver.
52 This interface can be used for out-of-band communication
58 Say Y here to enable the HD-audio codec re-configuration feature.
60 codec setup, add extra verbs, and re-configure the codec dynamically.
[all …]
|
| /linux-6.14.4/Documentation/driver-api/usb/ |
| D | gadget.rst | 11 This document presents a Linux-USB "Gadget" kernel mode API, for use
17 - Supports USB 2.0, for high speed devices which can stream data at
20 - Handles devices with dozens of endpoints just as well as ones with
21 just two fixed-function ones. Gadget drivers can be written so
24 - Flexible enough to expose more complex USB device capabilities such
28 - USB "On-The-Go" (OTG) support, in conjunction with updates to the
29 Linux-USB host side.
31 - Sharing data structures and API models with the Linux-USB host side
32 API. This helps the OTG support, and looks forward to more-symmetric
33 frameworks (where the same I/O model is used by both host and device
[all …]
|
| /linux-6.14.4/tools/perf/pmu-events/arch/powerpc/power9/ |
| D | translation.json | 20 "BriefDescription": "Double-Precion or Quad-Precision instruction completed"
25 …m another chip's memory on the same Node or Group (Distant) due to a data side request. When using…
35 …chip's L2 or L3 on the same Node or Group (Remote), as this chip due to a instruction side request"
60 … or L3 on a different Node or Group (Distant), as this chip due to a data side request. When using…
75 …ared or modified data from another core's L2/L3 on the same chip due to a instruction side request"
100 …e TLB from another chip's L4 on the same Node or Group ( Remote) due to a instruction side request"
115 …tions in 32 and 64 bit binary floating point format. Not qualified multicycle. Qualified by vector"
130 "BriefDescription": "Demand LD - L2 Miss (not L2 hit)"
140 …"BriefDescription": "The number a times the core transitioned from a stall to ICT-empty for this t…
145 …from a memory location including L4 from local remote or distant due to a instruction side request"
[all …]
|
| D | pipeline.json | 10 "BriefDescription": "Number of I-ERAT reloads"
25 …-cycle instruction issued to the Decimal Floating Point execution pipe and waiting to finish. Incl…
35 …her chip's L4 on a different Node or Group (Distant) due to a marked data side request. When using…
40 …s loaded into the TLB from local core's L2 without conflict due to a data side request. When using…
80 …ied (M) data from another core's L2 on the same chip due to a marked data side request. When using…
95 …h Modified (M) data from another core's L2 on the same chip due to a data side request. When using…
115 …e's L3 without dispatch conflicts hit on Mepf state. due to a marked data side request. When using…
135 …"BriefDescription": "Completion stall by Dcache miss which resolved on chip ( excluding local L2/L…
160 …core's L2/L3 on a different chip (remote or distant) due to a marked data side request. When using…
175 …ed into the TLB from local core's L3 with dispatch conflict due to a data side request. When using…
[all …]
|
| /linux-6.14.4/tools/testing/selftests/bpf/progs/ |
| D | cgroup_tcp_skb.c | 1 // SPDX-License-Identifier: GPL-2.0
29 if (skb->protocol != bpf_htons(ETH_P_IPV6)) in needed_tcp_pkt()
40 if (tcph->source != bpf_htons(g_sock_port) && in needed_tcp_pkt()
41 tcph->dest != bpf_htons(g_sock_port)) in needed_tcp_pkt()
51 if (tcph->fin || !tcph->syn || !tcph->ack) in egress_accept()
65 if (!tcph->syn || tcph->fin || tcph->ack) in ingress_accept()
71 if (tcph->fin || tcph->syn || !tcph->ack) in ingress_accept()
87 if (!tcph->syn || tcph->fin || tcph->ack) in egress_connect()
100 if (tcph->fin || !tcph->syn || !tcph->ack) in ingress_connect()
110 /* The connection is closed by the peer outside the cgroup. */
[all …]
|
| /linux-6.14.4/drivers/infiniband/ulp/rtrs/ |
| D | README | 11 possibility to either write data from an sg list to the remote side
12 or to request ("read") data transfer from the remote side into a given
15 RTRS provides I/O fail-over and load-balancing capabilities by using
17 Documentation/ABI/testing/sysfs-class-rtrs-client).
19 RTRS is used by the RNBD (RDMA Network Block Device) modules.
26 --------
29 server side for a given client for rdma transfer. A session
36 chunks reserved for him on the server side. Their number, size and addresses
49 discussed in LPC RDMA MC 2019. When always_invalidate=Y, on the server side we
64 ------------------------
[all …]
|
| /linux-6.14.4/tools/perf/pmu-events/arch/x86/snowridgex/ |
| D | uncore-interconnect.json | 49 …: "Coherent Ops : CLFlush : Counts the number of coherency related operations serviced by the IRP",
54 …"BriefDescription": "PCIITOM request issued by the IRP unit to the mesh with the intention of writ…
59 …"PublicDescription": "PCIITOM request issued by the IRP unit to the mesh with the intention of wri…
64 …"BriefDescription": "RFO request issued by the IRP unit to the mesh with the intention of writing …
70 …"PublicDescription": "RFO request issued by the IRP unit to the mesh with the intention of writing…
80 …": "Coherent Ops : WbMtoI : Counts the number of coherency related operations serviced by the IRP",
93 … "BriefDescription": "Inbound read requests received by the IRP and inserted into the FAF queue.",
98 …"PublicDescription": "Inbound read requests to coherent memory, received by the IRP and inserted i…
111 "BriefDescription": "FAF allocation -- sent to ADQ",
148 … "BriefDescription": "Counts Timeouts - Set 0 : Cache Inserts of Atomic Transactions as Secondary",
[all …]
|
12345678910>>...43