Searched full:operations (Results 1 – 25 of 2396) sorted by relevance
12345678910>>...96
| /Linux-v5.10/tools/perf/pmu-events/arch/arm64/hisilicon/hip08/ |
| D | uncore-hha.json | 5 "BriefDescription": "The number of all operations received by the HHA",
6 "PublicDescription": "The number of all operations received by the HHA",
12 "BriefDescription": "The number of all operations received by the HHA from another socket",
13 "PublicDescription": "The number of all operations received by the HHA from another socket",
19 …"BriefDescription": "The number of all operations received by the HHA from another SCCL in this so…
20 …"PublicDescription": "The number of all operations received by the HHA from another SCCL in this s…
26 "BriefDescription": "Count of the number of operations that HHA has received from CCIX",
27 "PublicDescription": "Count of the number of operations that HHA has received from CCIX",
33 "BriefDescription": "The number of read operations sent by HHA to DDRC which size is 64 bytes",
34 "PublicDescription": "The number of read operations sent by HHA to DDRC which size is 64bytes",
[all …]
|
| D | uncore-l3c.json | 68 "BriefDescription": "Count of the number of L3C back invalid operations",
69 "PublicDescription": "Count of the number of L3C back invalid operations",
75 "BriefDescription": "Count of the number of retry that L3C suppresses the CPU operations",
76 "PublicDescription": "Count of the number of retry that L3C suppresses the CPU operations",
82 "BriefDescription": "Count of the number of retry that L3C suppresses the ring operations",
83 "PublicDescription": "Count of the number of retry that L3C suppresses the ring operations",
|
| /Linux-v5.10/Documentation/ |
| D | atomic_bitops.txt | 5 While our bitmap_{}() functions are non-atomic, we have a number of operations
12 The single bit operations are:
18 RMW atomic operations without return value:
23 RMW atomic operations with return value:
33 All RMW atomic operations have a '__' prefixed variant which is non-atomic.
47 The test_and_{}_bit() operations return the original value of the bit.
55 - non-RMW operations are unordered;
57 - RMW operations that have no return value are unordered;
59 - RMW operations that have a return value are fully ordered.
61 - RMW operations that are conditional are unordered on FAILURE,
[all …]
|
| D | atomic_t.txt | 5 RMW operations between CPUs (atomic operations on MMIO are not supported and
20 RMW atomic operations:
85 the Non-RMW operations of atomic_t, you do not in fact need atomic_t at all
138 - plain operations without return value: atomic_{}()
140 - operations which return the modified value: atomic_{}_return()
142 these are limited to the arithmetic operations because those are
146 - operations which return the original value: atomic_fetch_{}()
148 - swap operations: xchg(), cmpxchg() and try_cmpxchg()
150 - misc; the special purpose operations that are commonly used and would,
155 All these operations are SMP atomic; that is, the operations (for a single
[all …]
|
| /Linux-v5.10/tools/perf/pmu-events/arch/x86/amdzen1/ |
| D | floating-point.json | 6 …operations (uOps) and dual-pipe uOps dispatched to each of the 4 FPU execution pipelines. This eve…
13 …operations (uOps) and dual-pipe uOps dispatched to each of the 4 FPU execution pipelines. This eve…
20 …operations (uOps) and dual-pipe uOps dispatched to each of the 4 FPU execution pipelines. This eve…
27 …operations (uOps) and dual-pipe uOps dispatched to each of the 4 FPU execution pipelines. This eve…
34 …operations (uOps) and dual-pipe uOps dispatched to each of the 4 FPU execution pipelines. This eve…
41 …operations (uOps) and dual-pipe uOps dispatched to each of the 4 FPU execution pipelines. This eve…
48 …operations (uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how bus…
55 …operations (uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how bus…
62 …operations (uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how bus…
69 …operations (uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how bus…
|
| /Linux-v5.10/Documentation/core-api/ |
| D | this_cpu_ops.rst | 2 this_cpu operations
8 this_cpu operations are a way of optimizing access to per cpu
14 this_cpu operations add a per cpu variable offset to the processor
24 Read-modify-write operations are of particular interest. Frequently
39 (remote write operations) of local RMW operations via this_cpu_*.
41 The main use of the this_cpu operations has been to optimize counter
42 operations.
44 The following this_cpu() operations with implied preemption protection
45 are defined. These operations can be used without worrying about
65 Inner working of this_cpu operations
[all …]
|
| D | local_ops.rst | 5 Semantics and Behavior of Local Atomic Operations
11 This document explains the purpose of the local atomic operations, how
18 Note that ``local_t`` based operations are not recommended for general
19 kernel use. Please use the ``this_cpu`` operations instead unless there is
21 replaced by ``this_cpu`` operations. ``this_cpu`` operations combine the
26 Purpose of local atomic operations
29 Local atomic operations are meant to provide fast and highly reentrant per CPU
30 counters. They minimize the performance cost of standard atomic operations by
39 Local atomic operations only guarantee variable modification atomicity wrt the
50 It can be done by slightly modifying the standard atomic operations: only
[all …]
|
| D | atomic_ops.rst | 2 Semantics and Behavior of Atomic and Bitmask Operations
11 Atomic Type And Operations
31 The first operations to implement for atomic_t's are the initializers and
41 The initializer is atomic in that the return values of the atomic operations
62 The setting is atomic in that the return values of the atomic operations by
74 values initialized or modified with the interface operations if a proper
77 interface operations. atomic_read does not guarantee that the runtime
180 locks, or atomic operations if variable a can change at runtime!
214 the operation. It must be done such that all memory operations before
273 with the given old and new values. Like all atomic_xxx operations,
[all …]
|
| /Linux-v5.10/tools/perf/pmu-events/arch/x86/westmereep-sp/ |
| D | floating-point.json | 91 "BriefDescription": "Computational floating-point operations executed"
123 "BriefDescription": "128 bit SIMD integer pack operations"
131 "BriefDescription": "128 bit SIMD integer arithmetic operations"
139 "BriefDescription": "128 bit SIMD integer logical operations"
147 "BriefDescription": "128 bit SIMD integer multiply operations"
155 "BriefDescription": "128 bit SIMD integer shift operations"
163 "BriefDescription": "128 bit SIMD integer shuffle/move operations"
171 "BriefDescription": "128 bit SIMD integer unpack operations"
179 "BriefDescription": "SIMD integer 64 bit pack operations"
187 "BriefDescription": "SIMD integer 64 bit arithmetic operations"
[all …]
|
| /Linux-v5.10/tools/perf/pmu-events/arch/x86/nehalemep/ |
| D | floating-point.json | 91 "BriefDescription": "Computational floating-point operations executed"
123 "BriefDescription": "128 bit SIMD integer pack operations"
131 "BriefDescription": "128 bit SIMD integer arithmetic operations"
139 "BriefDescription": "128 bit SIMD integer logical operations"
147 "BriefDescription": "128 bit SIMD integer multiply operations"
155 "BriefDescription": "128 bit SIMD integer shift operations"
163 "BriefDescription": "128 bit SIMD integer shuffle/move operations"
171 "BriefDescription": "128 bit SIMD integer unpack operations"
179 "BriefDescription": "SIMD integer 64 bit pack operations"
187 "BriefDescription": "SIMD integer 64 bit arithmetic operations"
[all …]
|
| /Linux-v5.10/tools/perf/pmu-events/arch/x86/nehalemex/ |
| D | floating-point.json | 91 "BriefDescription": "Computational floating-point operations executed"
123 "BriefDescription": "128 bit SIMD integer pack operations"
131 "BriefDescription": "128 bit SIMD integer arithmetic operations"
139 "BriefDescription": "128 bit SIMD integer logical operations"
147 "BriefDescription": "128 bit SIMD integer multiply operations"
155 "BriefDescription": "128 bit SIMD integer shift operations"
163 "BriefDescription": "128 bit SIMD integer shuffle/move operations"
171 "BriefDescription": "128 bit SIMD integer unpack operations"
179 "BriefDescription": "SIMD integer 64 bit pack operations"
187 "BriefDescription": "SIMD integer 64 bit arithmetic operations"
[all …]
|
| /Linux-v5.10/tools/perf/pmu-events/arch/x86/westmereep-dp/ |
| D | floating-point.json | 91 "BriefDescription": "Computational floating-point operations executed"
123 "BriefDescription": "128 bit SIMD integer pack operations"
131 "BriefDescription": "128 bit SIMD integer arithmetic operations"
139 "BriefDescription": "128 bit SIMD integer logical operations"
147 "BriefDescription": "128 bit SIMD integer multiply operations"
155 "BriefDescription": "128 bit SIMD integer shift operations"
163 "BriefDescription": "128 bit SIMD integer shuffle/move operations"
171 "BriefDescription": "128 bit SIMD integer unpack operations"
179 "BriefDescription": "SIMD integer 64 bit pack operations"
187 "BriefDescription": "SIMD integer 64 bit arithmetic operations"
[all …]
|
| /Linux-v5.10/tools/perf/pmu-events/arch/x86/westmereex/ |
| D | floating-point.json | 91 "BriefDescription": "Computational floating-point operations executed"
123 "BriefDescription": "128 bit SIMD integer pack operations"
131 "BriefDescription": "128 bit SIMD integer arithmetic operations"
139 "BriefDescription": "128 bit SIMD integer logical operations"
147 "BriefDescription": "128 bit SIMD integer multiply operations"
155 "BriefDescription": "128 bit SIMD integer shift operations"
163 "BriefDescription": "128 bit SIMD integer shuffle/move operations"
171 "BriefDescription": "128 bit SIMD integer unpack operations"
179 "BriefDescription": "SIMD integer 64 bit pack operations"
187 "BriefDescription": "SIMD integer 64 bit arithmetic operations"
[all …]
|
| /Linux-v5.10/tools/perf/pmu-events/arch/x86/amdzen2/ |
| D | floating-point.json | 6 …operations (uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how bus…
13 …operations (uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how bus…
20 …operations (uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how bus…
27 …operations (uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how bus…
34 …operations (uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how bus…
|
| /Linux-v5.10/Documentation/filesystems/caching/ |
| D | operations.rst | 4 Asynchronous Operations Handling
25 FS-Cache has an asynchronous operations handling facility that it uses for its
26 data storage and retrieval routines. Its operations are represented by
31 and FS-Cache will create operations and pass them off to the appropriate cache
75 operations:
81 This is, for example, used in read operations for calling readpages() on
121 Furthermore, operations may be one of two types:
123 (1) Exclusive (FSCACHE_OP_EXCLUSIVE). Operations of this type may not run in
129 (2) Shareable. Operations of this type may be running simultaneously. It's
131 operations running at the same time.
[all …]
|
| /Linux-v5.10/Documentation/virt/ |
| D | paravirt_ops.rst | 11 hypervisors. It allows each hypervisor to override critical operations and
15 pv_ops provides a set of function pointers which represent operations
18 time by enabling binary patching of the low-ops critical operations
21 pv_ops operations are classified into three categories:
24 These operations correspond to high level functionality where it is
28 Usually these operations correspond to low level critical instructions. They
|
| /Linux-v5.10/Documentation/filesystems/spufs/ |
| D | spufs.rst | 45 the operations supported on regular file systems. This list details the
46 supported operations and the deviations from the behaviour in the
51 All files support the access(2) and stat(2) family of operations, but
57 possible operations, e.g. read access on the wbox file.
65 data in the address space of the SPU. The possible operations on an
84 operations on an open mbox file are:
98 operations on an open ibox file are:
121 operations on an open wbox file are: write(2) If a count smaller than
143 operations on an open ``*box_stat`` file are:
173 The possible operations on an open npc, decr, decr_status,
[all …]
|
| /Linux-v5.10/Documentation/crypto/ |
| D | async-tx-api.rst | 15 3.2 Supported operations
36 the API will fit the chain of operations to the available offload
54 operations to be submitted, like xor->copy->xor in the raid5 case. The
71 3.2 Supported operations
97 operations complete. When an application needs to submit a chain of
98 operations it must guarantee that the descriptor is not automatically recycled
104 1. setting the ASYNC_TX_ACK flag if no child operations are to be submitted
112 Operations do not immediately issue after return from the
113 async_<operation> call. Offload engine drivers batch operations to
116 automatically issues pending operations. An application can force this
[all …]
|
| /Linux-v5.10/Documentation/arm/ |
| D | firmware.rst | 2 Interface for registering and calling firmware-specific operations for ARM
10 operations and call them when needed.
12 Firmware operations can be specified by filling in a struct firmware_ops
21 There is a default, empty set of operations provided, so there is no need to
22 set anything if platform does not require firmware operations.
33 Example of registering firmware operations::
52 /* other operations not available on platformX */
|
| /Linux-v5.10/include/drm/ |
| D | drm_gem_cma_helper.h | 40 * DEFINE_DRM_GEM_CMA_FOPS() - macro to generate file operations for CMA drivers
113 * DRM_GEM_CMA_DRIVER_OPS_WITH_DUMB_CREATE - CMA GEM driver operations
116 * This macro provides a shortcut for setting the default GEM operations in the
134 * DRM_GEM_CMA_DRIVER_OPS - CMA GEM driver operations
136 * This macro provides a shortcut for setting the default GEM operations in the
149 * DRM_GEM_CMA_DRIVER_OPS_VMAP_WITH_DUMB_CREATE - CMA GEM driver operations
154 * This macro provides a shortcut for setting the default GEM operations in the
173 * DRM_GEM_CMA_DRIVER_OPS_VMAP - CMA GEM driver operations ensuring a virtual
176 * This macro provides a shortcut for setting the default GEM operations in the
|
| /Linux-v5.10/Documentation/networking/ |
| D | nfc.rst | 21 responsible for providing an interface to control operations and low-level
24 The control operations are available to userspace via generic netlink.
36 | data exchange | operations
71 The userspace interface is divided in control operations and low-level data
74 CONTROL OPERATIONS:
76 Generic netlink is used to implement the interface to the control operations.
77 The operations are composed by commands and events, all listed below:
100 All polling operations requested through one netlink socket are stopped when
|
| /Linux-v5.10/tools/perf/pmu-events/arch/x86/icelake/ |
| D | floating-point.json | 38 … will count twice as noted below. Each count represents 2 computation operations, one for each el…
45 … will count twice as noted below. Each count represents 2 computation operations, one for each el…
49 … will count twice as noted below. Each count represents 4 computation operations, one for each el…
56 … will count twice as noted below. Each count represents 4 computation operations, one for each el…
60 … will count twice as noted below. Each count represents 4 computation operations, one for each el…
67 … will count twice as noted below. Each count represents 4 computation operations, one for each el…
71 … will count twice as noted below. Each count represents 8 computation operations, one for each el…
78 … will count twice as noted below. Each count represents 8 computation operations, one for each el…
82 … will count twice as noted below. Each count represents 8 computation operations, one for each el…
89 …will count twice as noted below. Each count represents 16 computation operations, one for each el…
[all …]
|
| /Linux-v5.10/Documentation/devicetree/bindings/dma/ |
| D | ste-dma40.txt | 60 bidirectional, i.e. the same for RX and TX operations:
113 51: memcpy TX (to be used by the DMA driver for memcpy operations)
118 56: memcpy (to be used by the DMA driver for memcpy operations)
119 57: memcpy (to be used by the DMA driver for memcpy operations)
120 58: memcpy (to be used by the DMA driver for memcpy operations)
121 59: memcpy (to be used by the DMA driver for memcpy operations)
122 60: memcpy (to be used by the DMA driver for memcpy operations)
|
| /Linux-v5.10/include/linux/ |
| D | coresight.h | 121 * @ops: generic operations for this component, as defined
125 * @groups: operations specific to this component. These will end up
175 * @ops: generic operations for this component, as defined
245 * struct coresight_ops_sink - basic operations for a sink
246 * Operations available for sinks
266 * struct coresight_ops_link - basic operations for a link
267 * Operations available for links.
277 * struct coresight_ops_source - basic operations for a source
278 * Operations available for sources.
296 * struct coresight_ops_helper - Operations for a helper device.
[all …]
|
| /Linux-v5.10/lib/ |
| D | test_fpu.c | 3 * Test cases for using floating point operations inside a kernel module.
12 * sequence of floating point operations. If the operations fail, either the
14 * If the operations succeed, the read returns "1\n".
25 * This sequence of operations tests that rounding mode is in test_fpu()
|
12345678910>>...96
