| /linux-5.10/lib/zlib_inflate/ |
| D | inflate.h | 18 HEAD, /* i: waiting for magic header */
19 FLAGS, /* i: waiting for method and flags (gzip) */
20 TIME, /* i: waiting for modification time (gzip) */
21 OS, /* i: waiting for extra flags and operating system (gzip) */
22 EXLEN, /* i: waiting for extra length (gzip) */
23 EXTRA, /* i: waiting for extra bytes (gzip) */
24 NAME, /* i: waiting for end of file name (gzip) */
25 COMMENT, /* i: waiting for end of comment (gzip) */
26 HCRC, /* i: waiting for header crc (gzip) */
27 DICTID, /* i: waiting for dictionary check value */
[all …]
|
| /linux-5.10/Documentation/scheduler/ |
| D | completion.rst | 22 until the result is actually needed, and both the waiting and the signalling
26 the Linux scheduler. The event the threads on the waitqueue are waiting for
39 - the waiting part through a call to one of the variants of wait_for_completion(),
43 Note that while initialization must happen first, the waiting and signaling
57 This provides the ->wait waitqueue to place tasks on for waiting (if any), and
122 must not return to a calling context until all activities (such as waiting
125 To emphasise this again: in particular when using some of the waiting API variants
141 Waiting for completions:
164 to wait_for_completion() then the waiting side simply will continue
181 time depending on the nature of the activity they are waiting for, so in
[all …]
|
| /linux-5.10/drivers/net/ethernet/qualcomm/ |
| D | qca_7k_common.h | 70 /* Waiting first 0xAA of header */
73 /* Waiting second 0xAA of header */
76 /* Waiting third 0xAA of header */
79 /* Waiting fourth 0xAA of header */
82 /* Waiting Byte 0-1 of length (litte endian) */
92 * Waiting for first 0x55 of footer
96 /* Waiting for second 0x55 of footer */
|
| /linux-5.10/drivers/cpuidle/ |
| D | coupled.c | 62 * the waiting loop, in the ready loop, or in the coupled idle state.
91 * @ready_waiting_counts: combined count of cpus in ready or waiting loops
119 * in use. This prevents a deadlock where two cpus are waiting for each others
215 * Decrements the ready counter, unless the ready (and thus the waiting) counter
217 * decrements the waiting counter and then re-increments it just before another
263 * cpuidle_coupled_cpus_waiting - check if all cpus in a coupled set are waiting
275 * cpuidle_coupled_no_cpus_waiting - check if no cpus in coupled set are waiting
278 * Returns true if all of the cpus in a coupled set are out of the waiting loop.
321 * cpuidle_coupled_poke - wake up a cpu that may be waiting
324 * Ensures that the target cpu exits it's waiting idle state (if it is in it)
[all …]
|
| /linux-5.10/include/linux/ |
| D | wait_bit.h | 63 * call wait_on_bit() in threads waiting for the bit to clear.
64 * One uses wait_on_bit() where one is waiting for the bit to clear,
89 * io_schedule() instead of schedule() for the actual waiting.
141 * to be cleared, and allow the waiting action to be specified.
142 * This is like wait_on_bit() but allows fine control of how the waiting
169 * and waiting for it to clear before setting it, one would call
170 * wait_on_bit() in threads waiting to be able to set the bit.
171 * One uses wait_on_bit_lock() where one is waiting for the bit to
196 * for the actual waiting.
219 * to be cleared and then to set it, and allow the waiting action
[all …]
|
| D | libps2.h | 26 #define PS2_FLAG_ACK BIT(0) /* Waiting for ACK/NAK */
27 #define PS2_FLAG_CMD BIT(1) /* Waiting for a command to finish */
28 #define PS2_FLAG_CMD1 BIT(2) /* Waiting for the first byte of command response */
31 #define PS2_FLAG_ACK_CMD BIT(5) /* Waiting to ACK the command (first) byte */
|
| D | rcupdate_wait.h | 13 * Structure allowing asynchronous waiting on RCU.
40 * on concurrent RCU and RCU-tasks grace periods. Waiting on a given SRCU
46 * bother waiting for RCU. The reason for this is because anywhere
|
| /linux-5.10/drivers/scsi/isci/ |
| D | request.h | 175 * waiting for the TC completion notification for the H2D Register FIS
178 * waiting for either a PIO Setup FIS or a D2H register FIS. The type of frame
182 * waiting for a DATA frame from the device.
185 * waiting to transmit the next data frame to the device.
188 * waiting for the TC completion notification for the H2D Register FIS
191 * waiting for either a PIO Setup.
195 * waiting for D2H status frame as UF.
202 * the started raw task management request is waiting for the transmission of
206 * management request is waiting for the reception of an unsolicited frame
210 * management request is waiting for the reception of an unsolicited frame
[all …]
|
| /linux-5.10/kernel/sched/ |
| D | completion.c | 7 * interface also makes it easy to 'complete' multiple waiting threads,
12 * Waiting for completion is a typically sync point, but not an exclusion point.
17 * complete: - signals a single thread waiting on this completion
20 * This will wake up a single thread waiting on this completion. Threads will be
42 * complete_all: - signals all threads waiting on this completion
45 * This will wake up all threads waiting on this particular completion event.
166 * interruptible and there is no timeout. The caller is accounted as waiting
182 * interruptible. The caller is accounted as waiting for IO (which traditionally
279 * enables us to avoid waiting if the resource the completion
|
| /linux-5.10/drivers/char/ipmi/ |
| D | kcs_bmc.h | 19 * BMC is waiting a last data byte from system software.
23 * BMC is waiting the response from the upper IPMI service.
27 * BMC is waiting error status request from system software.
29 * BMC is waiting for idle status afer error from system software.
|
| /linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-devices-waiting_for_supplier | 10 or 1) reflects whether the device is waiting for one or more
14 A value of 0 means the device is not waiting for any suppliers
16 is waiting for one or more suppliers to be added before it can
|
| D | sysfs-class-scsi_tape | 16 Shows the total amount of time spent waiting for all I/O
23 To determine the amount of time spent waiting for other I/O
64 Shows the total amount of time in nanoseconds waiting for
95 Shows the total amount of time in nanoseconds waiting for
|
| /linux-5.10/kernel/locking/ |
| D | qrwlock.c | 24 * Readers come here when they cannot get the lock without waiting in queued_read_lock_slowpath()
29 * if the writer is just waiting (not holding the lock yet), in queued_read_lock_slowpath()
31 * without waiting in the queue. in queued_read_lock_slowpath()
72 /* Set the waiting flag to notify readers that a writer is pending */ in queued_write_lock_slowpath()
|
| /linux-5.10/drivers/gpu/drm/vmwgfx/ |
| D | ttm_lock.h | 62 * @queue: Queue for processes waiting for lock change-of-status.
98 * @interruptible: Interruptible sleeping while waiting for a lock.
110 * @interruptible: Interruptible sleeping while waiting for a lock.
136 * @interruptible: Interruptible sleeping while waiting for a lock.
175 * @interruptible: Interruptible sleeping while waiting for a lock.
210 * @interruptible: Interruptible sleeping while waiting for a lock.
|
| /linux-5.10/Documentation/locking/ |
| D | robust-futex-ABI.rst | 24 call, and handles contested locking by maintaining a list of waiting
26 waiting on a particular futex, and waking up the next waiter on a
34 waiting on the same locks.
82 waiting for a lock on a threads exit if that next thread used the futex
90 indicating their holder died, and wakeup the next thread waiting for
168 they were waiting, and bit 30 is set by the kernel to indicate that the
|
| /linux-5.10/drivers/infiniband/core/ |
| D | iwcm.h | 38 IW_CM_STATE_LISTEN, /* listen waiting for connect */
39 IW_CM_STATE_CONN_RECV, /* inbound waiting for user accept */
40 IW_CM_STATE_CONN_SENT, /* outbound waiting for peer accept */
|
| /linux-5.10/tools/perf/pmu-events/arch/powerpc/power9/ |
| D | frontend.json | 70 …"BriefDescription": "Finish stall because the NTF instruction was a store waiting for a slot in th…
85 …"BriefDescription": "Finish stall because the NTF instruction was a stcx waiting for response from…
140 … NTF instruction was a mfspr instruction targeting an LSU SPR and it was waiting for the register …
165 …ause the NTF instruction was a store with all its dependencies met, just waiting to go through the…
225 …"BriefDescription": "Cycles in which the NTC instruction is waiting for a synchronous PMU interrup…
290 …"BriefDescription": "Finish stall because the next to finish instruction was a store waiting on da…
320 …"BriefDescription": "Finish stall because the NTF instruction was a store waiting for the next rel…
|
| D | metrics.json | 44 …all because the NTF instruction was routed to the crypto execution pipe and was waiting to finish",
50 … stall because the NTF instruction was a load that missed the L1 and was waiting for the data to r…
56 …ulti-cycle instruction issued to the Decimal Floating Point execution pipe and waiting to finish.",
68 …he NTF instruction was issued to the Decimal Floating Point execution pipe and waiting to finish.",
134 …s a scalar instruction issued to the Double Precision execution pipe and waiting to finish. Includ…
140 …ulti-cycle instruction issued to the Double Precision execution pipe and waiting to finish. Includ…
146 …"BriefDescription": "Finish stall because the NTF instruction is an EIEIO waiting for response fro…
294 … "BriefDescription": "Finish stall because the NTF instruction was a larx waiting to be satisfied",
300 …cause the NTF instruction was a load that hit on an older store and it was waiting for store data",
358 … NTF instruction was a mfspr instruction targeting an LSU SPR and it was waiting for the register …
[all …]
|
| /linux-5.10/include/uapi/linux/ |
| D | taskstats.h | 69 /* Delay waiting for cpu, while runnable
77 /* Delay waiting for synchronous block I/O to complete
83 /* Delay waiting for page fault I/O (swap in only) */
165 /* Delay waiting for memory reclaim */
169 /* Delay waiting for thrashing page */
|
| /linux-5.10/tools/testing/selftests/sync/ |
| D | sync_fence.c | 46 ASSERT(ret == 0, "Failure waiting on fence until timeout\n"); in test_fence_one_timeline_wait()
54 ASSERT(ret == 0, "Failure waiting on fence until timeout\n"); in test_fence_one_timeline_wait()
62 ASSERT(ret > 0, "Failure waiting on fence\n"); in test_fence_one_timeline_wait()
68 ASSERT(ret > 0, "Failure waiting ahead\n"); in test_fence_one_timeline_wait()
|
| /linux-5.10/tools/perf/pmu-events/arch/x86/sandybridge/ |
| D | uncore.json | 199 …"BriefDescription": "Counts cycles weighted by the number of requests waiting for data returning f…
200 …"PublicDescription": "Counts cycles weighted by the number of requests waiting for data returning …
271 …"BriefDescription": "Cycles with at least one request outstanding is waiting for data return from …
272 …"PublicDescription": "Cycles with at least one request outstanding is waiting for data return from…
283 …"BriefDescription": "Cycles with at least half of the requests outstanding are waiting for data re…
284 …"PublicDescription": "Cycles with at least half of the requests outstanding are waiting for data r…
|
| /linux-5.10/tools/perf/pmu-events/arch/x86/ivybridge/ |
| D | uncore.json | 199 …"BriefDescription": "Counts cycles weighted by the number of requests waiting for data returning f…
200 …"PublicDescription": "Counts cycles weighted by the number of requests waiting for data returning …
271 …"BriefDescription": "Cycles with at least one request outstanding is waiting for data return from …
272 …"PublicDescription": "Cycles with at least one request outstanding is waiting for data return from…
283 …"BriefDescription": "Cycles with at least half of the requests outstanding are waiting for data re…
284 …"PublicDescription": "Cycles with at least half of the requests outstanding are waiting for data r…
|
| /linux-5.10/drivers/infiniband/hw/hfi1/ |
| D | qp.h | 65 * HFI1_S_WAIT_PIO_DRAIN - qp waiting for PIOs to drain
66 * HFI1_S_WAIT_TID_SPACE - a QP is waiting for TID resource
67 * HFI1_S_WAIT_TID_RESP - waiting for a TID RDMA WRITE response
88 * Send if not busy or waiting for I/O and either
|
| /linux-5.10/drivers/usb/cdns3/ |
| D | drd.c | 154 dev_dbg(cdns->dev, "Waiting till Host mode is turned on\n"); in cdns3_drd_host_on()
159 dev_err(cdns->dev, "timeout waiting for xhci_ready\n"); in cdns3_drd_host_on()
177 /* Waiting till H_IDLE state.*/ in cdns3_drd_host_off()
198 dev_dbg(cdns->dev, "Waiting till Device mode is turned on\n"); in cdns3_drd_gadget_on()
204 dev_err(cdns->dev, "timeout waiting for dev_ready\n"); in cdns3_drd_gadget_on()
228 /* Waiting till DEV_IDLE state.*/ in cdns3_drd_gadget_off()
|
| /linux-5.10/include/rdma/ |
| D | rdmavt_qp.h | 62 * RVT_S_ACK_PENDING - an ACK is waiting to be sent after RDMA read/atomics
63 * RVT_S_WAIT_FENCE - waiting for all prior RDMA read or atomic SWQEs
65 * RVT_S_WAIT_RDMAR - waiting for a RDMA read or atomic SWQE to complete
67 * RVT_S_WAIT_RNR - waiting for RNR timeout
68 * RVT_S_WAIT_SSN_CREDIT - waiting for RC credits to process next SWQE
69 * RVT_S_WAIT_DMA - waiting for send DMA queue to drain before generating
71 * RVT_S_WAIT_PIO - waiting for a send buffer to be available
72 * RVT_S_WAIT_TX - waiting for a struct verbs_txreq to be available
73 * RVT_S_WAIT_DMA_DESC - waiting for DMA descriptors to be available
74 * RVT_S_WAIT_KMEM - waiting for kernel memory to be available
[all …]
|