Searched full:completion (Results 1 – 25 of 217) sorted by relevance
123456789
| /Documentation/translations/zh_CN/scheduler/ |
| D | completion.rst | 3 :Original: Documentation/scheduler/completion.rst
33 事件被简化为 ``struct completion`` 中的一个简单标志，被恰如其名地称为‘done’。
35 由于完成与调度有关，代码可以在kernel/sched/completion.c中找到。
43 - 'struct completion' 同步对象的初始化
51 要使用完成API，你需要#include <linux/completion.h>并创建一个静态或动态的
52 ``struct completion`` 类型的变量，它只有两个字段::
54 struct completion {
134 void wait_for_completion(struct completion *done)
140 struct completion setup_done;
180 int wait_for_completion_interruptible(struct completion *done)
[all …]
|
| /Documentation/scheduler/ |
| D | completion.rst | 2 Completions - "wait for completion" barrier APIs
27 is reduced to a simple flag in 'struct completion', appropriately called "done".
30 kernel/sched/completion.c.
38 - the initialization of the 'struct completion' synchronization object
45 to have marked a completion as 'done' before another thread checks whether
48 To use completions you need to #include <linux/completion.h> and
49 create a static or dynamic variable of type 'struct completion',
52 struct completion {
58 the ->done completion flag for indicating whether it's completed or not.
67 Good, intuitive naming (as always) helps code readability. Naming a completion
[all …]
|
| D | index.rst | 9 completion
|
| /Documentation/driver-api/usb/ |
| D | URB.rst | 36 - Each URB has a completion handler, which is called after the action
38 context-pointer for passing information to the completion handler.
42 data to an endpoint while your driver handles completion of another.
60 // (IN) all urbs need completion routines
61 void *context; // context for completion routine
62 usb_complete_t complete; // pointer to completion routine
64 // (OUT) status after each completion
110 returned to you in a completion callback. It will automatically be
122 length, the completion handler, and its context. Take a look at the some
156 never look at that value except in your completion callback.
[all …]
|
| /Documentation/arch/sparc/oradax/ |
| D | oracle-dax.rst | 41 pointer to a "completion area", which is a 128 byte memory block that
43 interrupt is generated upon completion; the completion area must be
46 processor until the completion status has been updated by the
52 completion of a request and resumption of execution of the requesting
85 call, and gets results (if any) via read(). The completion areas are
96 requests. The completion area buffer is also allocated, and this is
97 large enough to contain the completion areas for many concurrent
116 requests. Since no interrupt is generated upon the completion of a
142 completion area to use, and may be set via lseek() or using the
157 The mmap() function provides access to the completion area allocated
[all …]
|
| D | dax-hv-api.txt | 27 … of the submitted operations reported through a Completion Area linked to each CCB. Each CCB has a
28 …separate Completion Area and, unless execution order is specifically restricted through the use of…
29 …itional flags, the execution order of submitted CCBs is arbitrary. Likewise, the time to completion
197 [1:0] Completion area address type
209 with the Serial flag set. CCBs marked solely with the Serial flag will execute upon the completion …
210 previous Serial CCB, regardless of the completion status of that CCB. The Conditional flag allows C…
214 execute in parallel based on the completion of another CCB.
393 error in the completion area.
413 …The return value of the CCB completion area is invalid. The “number of elements processed” field i…
414 CCB completion area will be valid.
[all …]
|
| /Documentation/admin-guide/blockdev/drbd/ |
| D | disk-states-8.dot | 11 Consistent -> Failed [ label = "io completion error" ]
12 Outdated -> Failed [ label = "io completion error" ]
13 UpToDate -> Failed [ label = "io completion error" ]
14 Inconsistent -> Failed [ label = "io completion error" ]
|
| /Documentation/devicetree/bindings/scsi/ |
| D | hisilicon-sas.txt | 19 - queue-count : number of delivery and completion queues in the controller
21 - interrupts : For v1 hw: Interrupts for phys, completion queues, and fatal
24 - Completion queue interrupts
32 Completion queue interrupts : each completion queue has 1
38 For v2 hw: Interrupts for phys, Sata, and completion queues;
42 - Completion queue interrupts
49 Completion queue interrupts : each completion queue has 1
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | brcm,iproc-flexrm-mbox.txt | 23 The 2nd cell contains MSI completion threshold. This is the
24 number of completion messages for which FlexRM will inject
28 which FlexRM will wait to accumulate N completion messages
30 does not get required number of completion messages in time
32 to CPU provided at least one completion message is available.
|
| /Documentation/admin-guide/device-mapper/ |
| D | kcopyd.rst | 6 to one or more other block-devices, with an asynchronous completion
30 completion callback routine, and a pointer to some context data for the copy::
39 When the copy completes, kcopyd will call the user's completion routine,
|
| /Documentation/infiniband/ |
| D | core_locking.rst | 63 simultaneously. However, the ordering of the work completion
71 allowed for a low-level driver to call a consumer's completion event
77 completion event handlers for the same CQ are not called
93 The context in which completion event and asynchronous event
|
| /Documentation/driver-api/dmaengine/ |
| D | client.rst | 148 Although the async_tx API specifies that completion callback
189 after their transfer completion callback has run for the descriptor.
190 If no completion callback has been defined for the transfer, then the
193 completed, then the client must use completion callback.
247 3. on transfer completion, use dmaengine_desc_get_metadata_ptr() to get
255 point when the completion callback returns if used).
290 On completion of each DMA operation, the next in queue is started and
292 completion callback routine for notification, if set.
360 completion of a specific DMA transaction.
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-pci-devices-aer_stats | 49 Completion Timeout 0
51 Unexpected Completion 0
79 Completion Timeout 0
81 Unexpected Completion 0
|
| D | sysfs-class-net-queues | 105 Tx completion stall detection threshold in ms. Kernel will
114 Number of detected Tx completion stalls.
121 Longest detected Tx completion stall. Write 0 to clear.
|
| /Documentation/networking/device_drivers/ethernet/amazon/ |
| D | ena.rst | 68 - Admin Queue (AQ) and Admin Completion Queue (ACQ)
85 - Create I/O completion queue
87 - Destroy I/O completion queue
125 SQ correspondingly). Each SQ has a completion queue (CQ) associated
155 - Cache miss rate on completion is reduced, particularly for data
295 - When the ENA device finishes sending the packet, a completion
299 completion descriptors generated by the ENA, with a single
300 completion descriptor per completed packet.
302 * ``req_id`` is retrieved from the completion descriptor. The ``tx_info`` of
305 * The function stops when the completion descriptors are completed or
|
| /Documentation/crypto/ |
| D | async-tx-api.rst | 124 There are two methods for an application to learn about the completion
128 it polls for the completion of the operation. It handles dependency
130 2. Specify a completion callback. The callback routine runs in tasklet
136 completion interrupt/callback at the end of the chain.
143 2. Completion callback routines cannot submit new operations. This
172 struct completion cmp;
204 1. Completion callbacks are expected to happen in tasklet context
|
| /Documentation/driver-api/surface_aggregator/ |
| D | internal.rst | 79 workqueue for event and asynchronous request completion, and also manages
124 completed and provides the status of this completion, i.e. zero on success
135 * ``SSH_PACKET_SF_LOCKED_BIT``: This bit is set when completion, either
212 the successful completion of a sequenced packet will always run on the
213 receiver thread (whereas any failure-indicating completion will run on the
326 completion will occur once the underlying packet has been successfully
328 completion callback). For a request with response, successful completion
339 * ``SSH_REQUEST_SF_LOCKED_BIT``: This bit is set when completion, either
390 Packet Completion Callback
393 The packet completion callback is executed once the underlying packet of a
[all …]
|
| /Documentation/devicetree/bindings/interconnect/ |
| D | qcom,bcm-voter.yaml | 26 Optional mask of which TCSs (Triggered Command Sets) wait for completion
28 completion. The mask bits are available in the QCOM_ICC_TAG_* defines.
|
| /Documentation/networking/device_drivers/ethernet/huawei/ |
| D | hinic.rst | 69 Completion Event Queues(CEQs) - The completion Event Queues that describe IO
78 used to set the QPs addresses in HW. The commands completion events are
79 accumulated on the CEQ that is configured to receive the CMDQ completion events.
|
| /Documentation/networking/ |
| D | msg_zerocopy.rst | 23 it replaces per byte copy cost with page accounting and completion
104 previously passed buffer. It queues completion notifications on the
212 avoidance, and a contract that the kernel will queue a completion
221 In all these cases, the kernel returns a completion notification when
223 before the (copied) data is fully transmitted. A zerocopy completion
224 notification is not a transmit completion notification, therefore.
|
| D | tls-handshake.rst | 73 Completion" sesction below.
154 @sock has been canceled. The consumer's handshake completion callback
156 completion callback has already been invoked.
159 Handshake Completion
164 the consumer's handshake completion callback, provided in the @ta_done
212 Once the handshake completion callback function has been invoked, normal
|
| D | af_xdp.rst | 42 UMEM also has two rings: the FILL ring and the COMPLETION ring. The
46 COMPLETION ring, on the other hand, contains frame addr that the
49 COMPLETION ring are addrs that were previously transmitted using the
51 and the TX and COMPLETION rings are used for the TX path.
67 reason that there is only one set of FILL and COMPLETION rings per
128 There are a four different kind of rings: FILL, COMPLETION, RX and
133 The UMEM uses two rings: FILL and COMPLETION. Each socket associated
136 one FILL ring, one COMPLETION ring, four TX rings and four RX rings.
169 UMEM Completion Ring
172 The COMPLETION Ring is used transfer ownership of UMEM frames from
[all …]
|
| /Documentation/block/ |
| D | writeback_cache_control.rst | 9 write back caches. That means the devices signal I/O completion to the
37 filesystem and will make sure that I/O completion for this request is only
94 after the completion of the write request for bio submissions with the REQ_FUA
|
| /Documentation/mhi/ |
| D | mhi.rst | 64 Event rings: Used by the device to send completion and state transition messages
118 data transfer completion status, command completion status, and state changes
212 * Device generates a completion event for the processed TD by updating ED.
215 * Host wakes up and checks the event ring for completion event.
|
| /Documentation/networking/devlink/ |
| D | mlx5.rst | 147 - tx error completion
148 Report on error tx completion.
181 Report on rx completion error.
187 - Diagnose rx queues' status and corresponding completion queue::
263 number of times an EQ mapped to completion events was
|
123456789