Searched full:operation (Results 1 – 25 of 570) sorted by relevance
12345678910>>...23
| /Documentation/filesystems/caching/ |
| D | operations.txt | 11 (*) Operation record initialisation.
37 OPERATION RECORD INITIALISATION
40 An operation is recorded in an fscache_operation struct:
52 Someone wanting to issue an operation should allocate something with this
58 with the operation to be initialised and the release function to use.
67 operation and waited for afterwards.
74 There are a number of parameters that can be set in the operation record's flag
78 (1) The operation may be done synchronously (FSCACHE_OP_MYTHREAD). A thread
79 may decide it wants to handle an operation itself without deferring it to
89 before submitting the operation, and the operating thread must wait for it
[all …]
|
| D | backend-api.txt | 18 the fill_super() operation on mounting.
79 (1) that of the userspace process that issued the netfs operation that caused
139 passed to FS-Cache when requested by the appropriate cache operation. In
153 (*) FS-Cache operation record:
171 An operation can be made exclusive upon an object by setting the
173 an operation needs more processing time, it should be enqueued again.
176 (*) FS-Cache retrieval operation record:
187 backend to do the operation. The backend may get extra refs to it by
191 A retrieval operation can be used by the backend to do retrieval work. To
201 (*) FS-Cache storage operation record:
[all …]
|
| /Documentation/crypto/ |
| D | async-tx-api.txt | 11 3.4 When does the operation execute?
12 3.5 When does the operation complete?
30 that is written to the API can optimize for asynchronous operation and
44 operation will be offloaded when an engine is available and carried out
48 API automatically handles cases where the transition from one operation
50 3/ dmaengine extensions to support multiple clients and operation types
57 async_<operation>(<op specific parameters>, struct async_submit ctl *submit)
76 The return value is non-NULL and points to a 'descriptor' when the operation
90 3.4 When does the operation execute?
92 async_<operation> call. Offload engine drivers batch operations to
[all …]
|
| D | userspace-if.rst | 61 user space application. User space invokes the cipher operation with the
62 send()/write() system call family. The result of the cipher operation is
83 In-place Cipher operation
86 Just like the in-kernel operation of the kernel crypto API, the user
87 space interface allows the cipher operation in-place. That means that
96 operation.
101 The message digest type to be used for the cipher operation is selected
135 operation is performed without the initial HMAC state change caused by
141 The operation is very similar to the message digest discussion. During
168 - specification of the cipher operation type with one of these flags:
[all …]
|
| D | architecture.rst | 57 Synchronous And Asynchronous Operation
63 When using the synchronous API operation, the caller invokes a cipher
64 operation which is performed synchronously by the kernel crypto API.
65 That means, the caller waits until the cipher operation completes.
67 For synchronous operation, the set of API calls is small and
70 Asynchronous operation is provided by the kernel crypto API which
71 implies that the invocation of a cipher operation will complete almost
72 instantly. That invocation triggers the cipher operation but it does not
73 signal its completion. Before invoking a cipher operation, the caller
75 signal the completion of the cipher operation. Furthermore, the caller
[all …]
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | adc128d818.txt | 4 Operation modes:
18 If no operation mode is configured via device tree, the driver keeps the
19 currently active chip operation mode (default is mode 0).
29 - ti,mode: Operation mode (u8) (see above).
32 Example (operation mode 2):
|
| /Documentation/core-api/ |
| D | atomic_ops.rst | 64 been set with this operation or set with another operation. A proper implicit
65 or explicit memory barrier is needed before the value set with the operation
186 Now, we move onto the atomic operation interfaces typically implemented with
209 atomic_t and return the new counter value after the operation is
214 the operation. It must be done such that all memory operations before
215 and after the atomic operation calls are strongly ordered with respect
216 to the atomic operation itself.
219 before and after the atomic operation.
245 the atomic operation::
251 provide explicit memory barrier semantics around the operation::
[all …]
|
| /Documentation/media/uapi/dvb/ |
| D | fe-set-frontend.rst | 38 Points to parameters for tuning operation.
44 This ioctl call starts a tuning operation using specified parameters.
46 and the tuning could be initiated. The result of the tuning operation in
50 operation is initiated before the previous one was completed, the
51 previous operation will be aborted in favor of the new one. This command
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | tvp7002.txt | 21 0 = Normal Operation (Active Low, Default)
22 1 = Inverted operation
25 Under normal operation, the field ID output is set to logic 1 for an odd field
27 0 = Normal Operation (Active Low, Default)
|
| /Documentation/sound/designs/ |
| D | channel-mapping-api.rst | 52 Each control element provides at least the TLV read operation and the
53 read operation. Optionally, the write operation can be provided to
59 The TLV operation gives the list of available channel
144 Read Operation
147 The control read operation is for providing the current channel map of
155 Write Operation
158 The control write operation is optional, and only for devices that can
163 This operation is allowed only at PCM PREPARED state. When called in
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 18 result for an operation ... it doesn't indicate that anything is wrong
47 Also returned when trying to invoke an I2C operation in an
49 to execute some other operation.
68 detected before any I/O operation was started. Use a more
73 performing an I/O operation. Use a more specific fault
98 Returned by an adapter when asked to perform an operation
124 This is returned by drivers when an operation took too much
127 SMBus adapters may return it when an operation took more
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-ppi | 30 This attribute shows the request for an operation to be
40 This attribute shows the response to the most recent operation
51 a requested operation. The format is "<action num>: <action
60 operation to be executed in the pre-OS environment by the BIOS
71 operation to be executed in the pre-OS environment by the BIOS
|
| D | sysfs-class-typec | 9 as synchronous operation, so write(2) to the attribute will not
10 return until the operation has finished. The attribute is
24 Delivery. Swapping is supported as synchronous operation, so
25 write(2) to the attribute will not return until the operation
39 supported as a synchronous operation, so write(2) to the
40 attribute will not return until the operation has finished.
55 Swapping is supported as synchronous operation, so write(2) to
56 the attribute will not return until the operation has finished.
70 power operation mode means current level for VBUS. In case USB
72 power operation mode should show "usb_power_delivery".
|
| D | configfs-acpi | 21 will be enumerated. To check if the operation is
23 for close(). If the operation is successful,
|
| /Documentation/arm/ |
| D | firmware.rst | 24 To call a firmware operation, a helper macro is provided::
29 the macro checks if the operation is provided and calls it or otherwise returns
30 -ENOSYS to signal that given operation is not available (for example, to allow
31 fallback to legacy operation).
61 Example of using a firmware operation::
|
| /Documentation/xtensa/ |
| D | atomctl.rst | 2 Atomic Operation Control (ATOMCTL) Register
5 We Have Atomic Operation Control (ATOMCTL) Register.
27 support the Internal Operation.
49 2 Internal Operation Internal Operation Reserved
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | blkio-controller.rst | 147 are further divided by the type of operation - read or write, sync
149 device, third field specifies the operation type and the fourth field
154 are further divided by the type of operation - read or write, sync
156 device, third field specifies the operation type and the fourth field
168 the type of operation - read or write, sync or async. First two fields
170 specifies the operation type and the fourth field specifies the
183 devices too. This time is further divided by the type of operation -
185 minor number of the device, third field specifies the operation type
190 cgroup. This is further divided by the type of operation - read or
195 cgroup. This is further divided by the type of operation - read or
[all …]
|
| /Documentation/networking/ |
| D | nfc.txt | 61 * stop_poll - stop on progress polling operation
64 * data_exchange - send data and receive the response (transceive operation)
70 exchange operation.
79 * NFC_CMD_STOP_POLL - stop the polling operation in a specific device
90 operation by calling STOP_POLL command. In this case, it will be checked if
93 If the polling operation finds one or more targets, the event TARGETS_FOUND is
|
| D | lapb-module.txt | 82 0 LAPB operation (0=LAPB_STANDARD 1=LAPB_EXTENDED).
83 1 [SM]LP operation (0=LAPB_SLP 1=LAPB=MLP).
84 2 DTE/DCE operation (0=LAPB_DTE 1=LAPB_DCE)
87 Extended LAPB operation indicates the use of extended sequence numbers and
88 consequently larger window sizes, the default is standard LAPB operation.
89 MLP operation is the same as SLP operation except that the addresses used by
90 LAPB are different to indicate the mode of operation, the default is Single
91 Link Procedure. The difference between DCE and DTE operation is (i) the
|
| /Documentation/devicetree/bindings/rtc/ |
| D | isil,isl12026.txt | 15 value for proper operation.
18 value for proper operation.
|
| /Documentation/infiniband/ |
| D | tag_matching.rst | 17 matching operation. However, this doesn’t imply that tags are consumed in
22 library may attempt to process the operation either after or before the
38 the header to initiate an RDMA READ operation directly to the matching buffer.
66 tightly synchronized with respect to the tag-matching operation, this shadow
|
| /Documentation/ |
| D | this_cpu_ops.txt | 15 specific per cpu base and encode that operation in the instruction
19 the offset and the operation on the data. Therefore it is not
22 the operation on the data.
91 Consider the following this_cpu operation::
142 Note that this operation is usually used in a code segment when
222 these per cpu local operations. In that case the operation must be
233 still occur while an operation is in progress and if the interrupt too
256 address relocation and a Read-Modify-Write operation in the same
263 The first operation takes the offset and forms an address and then
285 RMW operation.
|
| /Documentation/admin-guide/device-mapper/ |
| D | delay.rst | 23 # Create device delaying rw operation for 500ms
29 # Create device delaying only write operation for 500ms and
|
| /Documentation/devicetree/bindings/usb/ |
| D | dwc3-xilinx.txt | 8 operation and >= 60MHz for HS operation
|
| /Documentation/admin-guide/laptops/ |
| D | disk-shock-protection.rst | 47 normal operation will be resumed. The maximal value accepted for a
54 cancel a previously set timeout and resume normal operation
59 of milliseconds remaining until normal operation will be resumed;
71 will show you how many milliseconds are left before normal operation
77 unload operation to complete is vendor specific. The hint in ATA-7
102 will generally not affect the mode of operation of another drive
|
12345678910>>...23