| /linux-5.19.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-5.19.10/tools/memory-model/Documentation/ ! |
| D | ordering.txt | 2 operations provided by the Linux-kernel memory model (LKMM).
9 operations in decreasing order of strength:
12 all of the CPU's prior operations against some or all of its
13 subsequent operations.
15 2. Ordered memory accesses. These operations order themselves
23 some of these "unordered" operations provide limited ordering
62 o Value-returning RMW atomic operations whose names do not end in
82 Second, some RMW atomic operations provide full ordering. These
83 operations include value-returning RMW atomic operations (that is, those
86 cmpxchg(), and xchg(). Note that conditional RMW atomic operations such
[all …]
|
| /linux-5.19.10/Documentation/bpf/ ! |
| D | instruction-set.rst | 50 BPF_LD 0x00 non-standard load operations
51 BPF_LDX 0x01 load into register operations
52 BPF_ST 0x02 store from immediate operations
53 BPF_STX 0x03 store from register operations
54 BPF_ALU 0x04 32-bit arithmetic operations
55 BPF_JMP 0x05 64-bit jump operations
56 BPF_JMP32 0x06 32-bit jump operations
57 BPF_ALU64 0x07 64-bit arithmetic operations
88 otherwise identical operations.
107 BPF_END 0xd0 byte swap operations (see separate section below)
[all …]
|
| /linux-5.19.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-5.19.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-5.19.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 | 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
63 Rules to follow when using local atomic operations
[all …]
|
| /linux-5.19.10/mm/damon/ ! |
| D | Kconfig | 28 bool "Data access monitoring operations for virtual address spaces"
32 This builds the default data access monitoring operations for DAMON
36 bool "Data access monitoring operations for the physical address space"
40 This builds the default data access monitoring operations for DAMON
44 bool "Test for DAMON operations" if !KUNIT_ALL_TESTS
48 This builds the DAMON virtual addresses operations Kunit test suite.
|
| /linux-5.19.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)
|
| D | mv-xor.txt | 20 - dmacap,memcpy to indicate that the XOR channel is capable of memcpy operations
21 - dmacap,memset to indicate that the XOR channel is capable of memset operations
22 - dmacap,xor to indicate that the XOR channel is capable of xor operations
|
| /linux-5.19.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
113 async_<operation> call. Offload engine drivers batch operations to
116 automatically issues pending operations. An application can force this
129 chains and issuing pending operations.
[all …]
|
| /linux-5.19.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
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-5.19.10/Documentation/admin-guide/perf/ ! |
| D | hisi-pmu.rst | 64 This will only count the operations from core/thread 0 and 1 in this cluster.
67 operations via the tt_req parameeter in perf. The default value counts all
68 operations. tt_req is 3bits, 3'b100 represents read operations, 3'b101
69 represents write operations, 3'b110 represents atomic store operations and
70 3'b111 represents atomic non-store operations, other values are reserved::
74 This will only count the read operations in this cluster.
|
| /linux-5.19.10/Documentation/driver-api/ ! |
| D | clk.rst | 17 gating, rate adjustment, muxing or other operations. This framework is
25 drivers/clk/clk.c. Finally there is struct clk_ops, whose operations
67 the operations defined in clk-provider.h::
175 To take advantage of your data you'll need to support valid operations
271 .disable operations. Those operations are thus not allowed to sleep,
285 The prepare lock is a mutex and is held across calls to all other operations.
286 All those operations are allowed to sleep, and calls to the corresponding API
289 This effectively divides operations in two groups from a locking perspective.
291 Drivers don't need to manually protect resources shared between the operations
293 clocks or not. However, access to resources that are shared between operations
[all …]
|
| D | i2c.rst | 26 are functions to perform various I2C protocol operations; at this writing
32 Controllers that support I2C can also support most SMBus operations, but
35 operations, either using I2C primitives or by issuing SMBus commands to
36 i2c_adapter devices which don't support those I2C operations.
|
| /linux-5.19.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-5.19.10/Documentation/arm/vfp/ ! |
| D | release-notes.rst | 19 The operations which have been tested with this package are:
41 Other operations which have been tested by basic assembly-only tests
51 The combination operations have not been tested:
|
| /linux-5.19.10/Documentation/ABI/testing/ ! |
| D | debugfs-pfo-nx-crypto | 33 The total number of AES operations submitted to the hardware.
39 The total number of SHA-256 operations submitted to the hardware.
45 The total number of SHA-512 operations submitted to the hardware.
|
| /linux-5.19.10/net/rds/ ! |
| D | Kconfig | 15 This transport supports RDMA operations.
23 This transport does not support RDMA operations.
|
| /linux-5.19.10/Documentation/vm/damon/ ! |
| D | design.rst | 17 level primitives implementations monitoring operations.
21 monitoring operations. If appropriate one is not provided, users can implement
22 the operations on their own.
33 The monitoring operations are defined in two parts:
38 DAMON currently provides the implementations of the operations for the physical
45 This is only for the virtual address space monitoring operations
173 monitoring operations to check dynamic changes including memory mapping changes
174 and applies it to monitoring operations-related data structures such as the
|
| /linux-5.19.10/Documentation/driver-api/soundwire/ ! |
| D | locking.rst | 6 following locks in order to avoid race conditions in Bus operations on
18 serialize each of the following operations(s) within SoundWire Bus instance.
22 - Prepare, Enable, Disable and De-prepare stream operations.
|
| D | stream.rst | 197 framework(ASoC DPCM) guarantees that stream operations on a card are
228 SoundWire Bus manages stream operations for each stream getting
229 rendered/captured on the SoundWire Bus. This section explains Bus operations
267 Below section explains the operations done by the Bus on Master(s) and
277 runtime is used as a reference for all the operations performed
285 After all above operations are successful, stream state is set to
315 After all above operations are successful, stream state is set to
365 After all above operations are successful, stream state is set to
370 to .prepare() operation. Since the .trigger() operations may not
397 After all above operations are successful, stream state is set to
[all …]
|
| /linux-5.19.10/Documentation/translations/zh_CN/locking/ ! |
| D | spinlocks.rst | 35 (5) ACQUIRE operations.
37 (6) RELEASE operations.
|
| /linux-5.19.10/Documentation/translations/zh_CN/admin-guide/mm/damon/ ! |
| D | usage.rst | 50 # echo vaddr > kdamonds/0/contexts/0/operations
65 │ │ │ │ 0/operations
130 在每个上下文目录中，存在一个文件(``operations``)和三个目录(``monitoring_attrs``,
164 如果你把 ``vaddr`` 写到 ``contexts/<N>/operations`` 中，每个目标应该是一个进程。你
170 当使用 ``vaddr`` 监测操作集时（ ``vaddr`` 被写入 ``contexts/<N>/operations`` 文
175 被写入 ``contexts/<N>/operations`` 中）。因此，在这种情况下，用户应该自己设置监测目标
|