Searched +full:side +full:- +full:by +full:- +full:side (Results 1 – 25 of 1133) sorted by relevance
12345678910>>...46
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/silvermont/ |
| D | virtual-memory.json | 13 …ce a page walk implies a TLB miss, the number of TLB misses can be counted by counting the number … 19 "BriefDescription": "D-side page-walks", 23 …when a D-side (walks due to a load) page walk is in progress. Page walk duration divided by number… 29 "BriefDescription": "Duration of D-side page-walks in core cycles" 32 …ce a page walk implies a TLB miss, the number of TLB misses can be counted by counting the number … 38 "BriefDescription": "I-side page-walks", 42 …I-side (walks due to an instruction fetch) page walk is in progress. Page walk duration divided by… 48 "BriefDescription": "Duration of I-side page-walks in core cycles" 51 …ce a page walk implies a TLB miss, the number of TLB misses can be counted by counting the number … 57 "BriefDescription": "Total page walks that are completed (I-side and D-side)", [all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/silvermont/ |
| D | virtual-memory.json | 12 "BriefDescription": "Total cycles for all the page walks. (I-side and D-side)", 20 "BriefDescription": "Duration of D-side page-walks in core cycles", 23 …when a D-side (walks due to a load) page walk is in progress. Page walk duration divided by number… 28 "BriefDescription": "D-side page-walks", 32 …ce a page walk implies a TLB miss, the number of TLB misses can be counted by counting the number … 37 "BriefDescription": "Duration of I-side page-walks in core cycles", 40 …I-side (walks due to an instruction fetch) page walk is in progress. Page walk duration divided by… 45 "BriefDescription": "I-side page-walks", 49 …ce a page walk implies a TLB miss, the number of TLB misses can be counted by counting the number … 54 "BriefDescription": "Total page walks that are completed (I-side and D-side)", [all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/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 40 RCU does allow -readers- to run (almost) naked, but -writers- must 49 them -- even x86 allows later loads to be reordered to precede 55 by definition can be no bottleneck). Note that the definition [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. 31 Check for RCU read-side critical section. 33 Check for RCU-bh read-side critical section. 35 Check for RCU-sched read-side critical section. 37 Check for SRCU read-side critical section. 41 invoked by both RCU readers and updaters. 45 is invoked by both RCU-bh readers and updaters. [all …]
|
| D | whatisRCU.rst | 3 What is RCU? -- "Read, Copy, Update" 21 during the 2.5 development effort that is optimized for read-mostly 40 :ref:`6. ANALOGY WITH READER-WRITER LOCKING <6_whatisRCU>` 47 Section 1, though most readers will profit by reading this section at 52 into the kernel source code. People who reason best by analogy should 58 everything, feel free to read the whole thing -- but if you are really 60 never need this document anyway. ;-) 65 ---------------- 69 within a data structure (possibly by replacing them with references to 83 completed, either by blocking until they finish or by registering a [all …]
|
| /kernel/linux/linux-6.6/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 <Frank.Li@nxp.com> 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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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 (alborchers@steinerpoint.com). 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 …]
|
| /kernel/linux/linux-6.6/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 (alborchers@steinerpoint.com). 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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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. 56 This driver provides kernel-side support for the Random Number [all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/ivytown/ |
| D | uncore-cache.json | 13 …ted information by filtering the Cb0 occupancy count captured in Counter 0. The filtering availa… 21 … LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has numer… 30 … LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has numer… 39 …- this includes code, data, prefetches and hints coming from L2. This has numerous filters availa… 48 … LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has numer… 57 …- this includes code, data, prefetches and hints coming from L2. This has numerous filters availa… 66 … the number of lines that were victimized on a fill. This can be filtered by the state that the l… 75 … 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… 93 …imized on a fill. This can be filtered by the state that the line was in.; Qualify one of the oth… [all …]
|
| /kernel/linux/linux-5.10/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 <#Summary>`__, however, the answers to 53 ------------------------ [all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/devfreq/ |
| D | rk3399_dmc.txt | 4 - compatible: Must be "rockchip,rk3399-dmc". 5 - devfreq-events: Node to get DDR loading, Refer to 7 rockchip-dfi.txt 8 - clocks: Phandles for clock specified in "clock-names" property 9 - clock-names : The name of clock used by the DFI, must be 11 - operating-points-v2: Refer to Documentation/devicetree/bindings/opp/opp.txt 13 - center-supply: DMC supply node. 14 - status: Marks the node enabled/disabled. 17 - interrupts: The CPU interrupt number. The interrupt specifier 21 - rockchip,pmu: Phandle to the syscon managing the "PMU general register [all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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 - 70 * srcu_read_lock_held - might we be in SRCU read-side critical section? 74 * read-side critical section. In absence of CONFIG_DEBUG_LOCK_ALLOC, 75 * this assumes we are in an SRCU read-side critical section unless it can 89 return lock_is_held(&ssp->dep_map); in srcu_read_lock_held() 102 * srcu_dereference_check - fetch SRCU-protected pointer for later dereferencing 105 * really are in an SRCU read-side critical section. 106 * @c: condition to check for update-side use [all …]
|
| /kernel/linux/linux-6.6/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 …]
|
12345678910>>...46