waiting (full) in projects: Linux-v6.6 - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:waiting (Results 1 – 25 of 2750) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...110

/Linux-v6.6/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-v6.6/tools/perf/pmu-events/arch/powerpc/power10/
D	pipeline.json	55 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was waiting for a load… 85 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was waiting for a load… 95 …iption": "Cycles in which the oldest instruction in the pipeline was a lwsync waiting to complete." 150 …"BriefDescription": "Cycles when dispatch was stalled while waiting to resolve an instruction ERAT… 155 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was waiting for a load… 160 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was waiting for a load… 205 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was a stcx waiting for… 250 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was waiting to finish … 265 …n which the next-to-complete (NTC) instruction is held at dispatch while waiting on the Scoreboard… 275 …pipeline was a store whose cache line was not resident in the L1 and was waiting for allocation of… [all …]
D	metrics.json	40 …on": "Average cycles per completed instruction when dispatch was stalled waiting to resolve an ins… 46 …on": "Average cycles per completed instruction when dispatch was stalled waiting to resolve an ins… 118 …ompleted instruction when the NTC instruction was held at dispatch while waiting on the scoreboard… 160 …": "Average cycles per completed instruction when the NTC instruction is waiting to be finished in… 196 …": "Average cycles per completed instruction when the NTC instruction is waiting to be finished in… 226 …": "Average cycles per completed instruction when the NTC instruction is waiting for a load miss t… 232 …": "Average cycles per completed instruction when the NTC instruction is waiting for a load miss t… 238 …": "Average cycles per completed instruction when the NTC instruction is waiting for a load miss t… 244 …": "Average cycles per completed instruction when the NTC instruction is waiting for a load miss t… 250 …": "Average cycles per completed instruction when the NTC instruction is waiting for a load miss t… [all …]
/Linux-v6.6/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-v6.6/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-v6.6/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-v6.6/tools/testing/selftests/arm64/abi/
D	tpidr2.c	`98 pid_t newpid, waiting, oldpid; in write_fork_read() local 130 waiting = waitpid(newpid, &status, 0); in write_fork_read() 132 if (waiting < 0) { in write_fork_read() 140 if (waiting != newpid) { in write_fork_read() 180 pid_t parent, waiting; in write_clone_read() local 215 waiting = wait4(ret, &status, __WCLONE, NULL); in write_clone_read() 217 if (waiting < 0) { in write_clone_read() 225 if (waiting != ret) { in write_clone_read() 227 putnum(waiting); in write_clone_read()`
/Linux-v6.6/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	rcupdate_wait.h	`13 * Structure allowing asynchronous waiting on RCU. 40 * on concurrent RCU and RCU-tasks grace periods. Waiting on a given SRCU 51 * bother waiting for RCU. The reason for this is because anywhere`
/Linux-v6.6/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-v6.6/include/uapi/linux/
D	taskstats.h	`70 /* Delay waiting for cpu, while runnable 78 /* Delay waiting for synchronous block I/O to complete 84 /* Delay waiting for page fault I/O (swap in only) / 166 / Delay waiting for memory reclaim / 170 / Delay waiting for thrashing page / 177 / v11: Delay waiting for memory compact / 198 / v13: Delay waiting for write-protect copy / 202 / v14: Delay waiting for IRQ/SOFTIRQ */`
D	dma-buf.h	`49 * synchronization, waiting for prior work to complete can be done via 96 * dma-buf for waiting later instead of waiting immediately. This is 126 * complete. Waiting on the returned sync file is equivalent to 130 * any users of the dma-buf (read or write) to complete. Waiting`
/Linux-v6.6/tools/perf/pmu-events/arch/arm64/arm/cortex-a55/
D	pipeline.json	33 …talled and there is an interlock that is due to a load/store instruction waiting for data to calcu… 36 …talled and there is an interlock that is due to a load/store instruction waiting for data to calcu… 57 …unts every cycle there is a stall in the Wr stage due to a load which is waiting on data (due to m… 60 …unts every cycle there is a stall in the Wr stage due to a load which is waiting on data (due to m… 69 …nts every cycle there is a stall in the Wr stage due to a store which is waiting due to the STB be… 72 …nts every cycle there is a stall in the Wr stage due to a store which is waiting due to the STB be…
/Linux-v6.6/kernel/sched/
D	completion.c	8 * interface also makes it easy to 'complete' multiple waiting threads, 13 * Waiting for completion is a typically sync point, but not an exclusion point. 34 * complete: - signals a single thread waiting on this completion 37 * This will wake up a single thread waiting on this completion. Threads will be 52 * complete_all: - signals all threads waiting on this completion 55 * This will wake up all threads waiting on this particular completion event. 176 * interruptible and there is no timeout. The caller is accounted as waiting 192 * interruptible. The caller is accounted as waiting for IO (which traditionally 301 * enables us to avoid waiting if the resource the completion
/Linux-v6.6/drivers/vdpa/solidrun/
D	snet_ctrl.c	157 SNET_WARN(pdev, "Timeout waiting for previous control data to be consumed\n"); in snet_ctrl_read_from_dpu() 175 SNET_WARN(pdev, "Timeout waiting for control data\n"); in snet_ctrl_read_from_dpu() 208 SNET_WARN(pdev, "Timeout waiting for the DPU to complete a control command\n"); in snet_ctrl_read_from_dpu() 232 SNET_WARN(pdev, "Timeout waiting for previous control message to be ACKed\n"); in snet_send_ctrl_msg_old() 242 SNET_WARN(pdev, "Timeout waiting for a control message to be ACKed\n"); in snet_send_ctrl_msg_old() 268 SNET_WARN(pdev, "Timeout waiting for previous control data to be consumed\n"); in snet_send_ctrl_msg() 288 SNET_WARN(pdev, "Timeout waiting for control message to be ACKed\n"); in snet_send_ctrl_msg() 302 SNET_WARN(pdev, "Timeout waiting for DPU to complete a control command, err %d\n", in snet_send_ctrl_msg()
/Linux-v6.6/tools/perf/pmu-events/arch/arm64/arm/cortex-a75/
D	pipeline.json	`27 … the cycles where all slots in the LS IQs are full with micro-operations waiting for issuing, and … 30 … the cycles where all slots in the LS IQs are full with micro-operations waiting for issuing, and … 33 …es where all slots in the DP0 and DP1 IQs are full with micro-operations waiting for issuing, and … 36 …es where all slots in the DP0 and DP1 IQs are full with micro-operations waiting for issuing, and …`
/Linux-v6.6/tools/testing/selftests/arm64/fp/
D	za-fork.c	`26 pid_t newpid, waiting; in fork_test_c() local 50 waiting = waitpid(newpid, &child_status, 0); in fork_test_c() 52 if (waiting < 0) { in fork_test_c() 58 if (waiting != newpid) { in fork_test_c()`
/Linux-v6.6/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-v6.6/tools/perf/pmu-events/arch/arm64/arm/cortex-a510/
D	pipeline.json	45 …ss operand. This type of interlock is caused by a load/store instruction waiting for data to calcu… 48 …ss operand. This type of interlock is caused by a load/store instruction waiting for data to calcu… 69 …every cycle where there is a stall in the Wr stage due to a load that is waiting on data. The even… 72 …every cycle where there is a stall in the Wr stage due to a load that is waiting on data. The even… 81 …re there is a stall in the Wr stage because of a store operation that is waiting due to the STB be… 84 …re there is a stall in the Wr stage because of a store operation that is waiting due to the STB be…
/Linux-v6.6/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() 80 /* Set the waiting flag to notify readers that a writer is pending */ in queued_write_lock_slowpath()`
/Linux-v6.6/drivers/infiniband/hw/hfi1/
D	qp.h	`23 * HFI1_S_WAIT_PIO_DRAIN - qp waiting for PIOs to drain 24 * HFI1_S_WAIT_TID_SPACE - a QP is waiting for TID resource 25 * HFI1_S_WAIT_TID_RESP - waiting for a TID RDMA WRITE response 46 * Send if not busy or waiting for I/O and either`
/Linux-v6.6/tools/perf/pmu-events/arch/powerpc/power9/
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-v6.6/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-v6.6/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 */`

12 3 4 5 6 7 8 9 10 >>...110