| /linux/Documentation/ |
| A 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 …]
|
| A D | atomic_t.txt | 5 RMW operations between CPUs (atomic operations on MMIO are not supported and
20 RMW atomic operations:
138 - plain operations without return value: atomic_{}()
146 - operations which return the original value: atomic_fetch_{}()
148 - swap operations: xchg(), cmpxchg() and try_cmpxchg()
155 All these operations are SMP atomic; that is, the operations (for a single
165 - non-RMW operations are unordered;
167 - RMW operations that have no return value are unordered;
169 - RMW operations that have a return value are fully ordered;
171 - RMW operations that are conditional are unordered on FAILURE,
[all …]
|
| /linux/tools/memory-model/Documentation/ |
| A D | ordering.txt | 2 operations provided by the Linux-kernel memory model (LKMM).
9 operations in decreasing order of strength:
13 subsequent operations.
83 operations include value-returning RMW atomic operations (that is, those
247 a. Release operations.
249 b. Acquire operations.
292 There is a wide variety of release operations:
443 a. Unordered marked operations.
457 These operations come in three categories:
465 operations, unless these operations are to the same variable.
[all …]
|
| /linux/Documentation/arm/ |
| A 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/Documentation/virt/ |
| A 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/Documentation/core-api/ |
| A 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_*.
42 operations.
45 are defined. These operations can be used without worrying about
65 Inner working of this_cpu operations
128 Special operations
167 cpu variable. Most this_cpu operations take a cpu variable.
[all …]
|
| A 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/Documentation/crypto/ |
| A 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
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.
143 2. Completion callback routines cannot submit new operations. This
207 handle submission of dependent operations
[all …]
|
| /linux/Documentation/devicetree/bindings/dma/ |
| A 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)
|
| A 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/Documentation/networking/ |
| A 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/Documentation/admin-guide/perf/ |
| A 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/Documentation/filesystems/spufs/ |
| A 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/Documentation/driver-api/ |
| A 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
299 framework functions from within its implementation of clock operations. This
[all …]
|
| A 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/Documentation/filesystems/caching/ |
| A D | operations.rst | 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:
131 operations running at the same time.
160 The operation manager will defer operations on an object that is still
|
| /linux/Documentation/arm/vfp/ |
| A 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/Documentation/ABI/testing/ |
| A 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.
|
| A D | sysfs-bus-i2c-devices-pca954x | 16 setting in terms of I2C operations and is the
21 latency for normal operations after rare
|
| /linux/Documentation/driver-api/soundwire/ |
| A 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
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
425 After all above operations are successful, stream state is set to
458 After all above operations are successful, stream state is set to
[all …]
|
| A 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.
|
| /linux/Documentation/scsi/ |
| A D | ufs.rst | 74 It handles device level operations and device
75 configuration operations. Device level operations mainly involve
76 device power management operations and commands to Interconnect
89 manager for device level operations. These device level operations
|
| /linux/net/rds/ |
| A D | Kconfig | 15 This transport supports RDMA operations.
23 This transport does not support RDMA operations.
|
| /linux/Documentation/devicetree/bindings/powerpc/opal/ |
| A D | sensor-groups.txt | 17 operations like clearing the min/max history of all
25 - ops : Array of opal-call numbers indicating available operations on
|
| /linux/Documentation/filesystems/ |
| A D | netfs_library.rst | 13 - Read helper operations.
22 network filesystem in implementing VM/VFS operations. For the moment, that
23 just includes turning various VM buffered read operations into requests to read
35 ->readahead() and much of the ->write_begin() VM operations and translate them
63 From the network filesystem, the helpers require a table of operations. This
110 through the suppplied table of operations. Waits will be performed as
261 The operations are as follows:
281 of operations of its own there (though of a different type).
404 * Synchronous operations will wait for reading to be complete.
417 read request and a table of operations for the helpers to call.
[all …]
|