/linux-4.4.14/drivers/isdn/gigaset/ |
D | proc.c | 43 cs->waiting = 1; in set_cidmode() 46 cs->waiting = 0; in set_cidmode() 52 wait_event(cs->waitqueue, !cs->waiting); in set_cidmode()
|
D | common.c | 526 at_state->waiting = 0; in gigaset_at_init() 708 cs->waiting = 0; in gigaset_initcs() 861 if (cs->waiting) { in cleanup_cs() 863 cs->waiting = 0; in cleanup_cs() 898 cs->waiting = 1; in gigaset_start() 901 cs->waiting = 0; in gigaset_start() 906 wait_event(cs->waitqueue, !cs->waiting); in gigaset_start() 936 cs->waiting = 1; in gigaset_shutdown() 942 wait_event(cs->waitqueue, !cs->waiting); in gigaset_shutdown() 963 cs->waiting = 1; in gigaset_stop() [all …]
|
D | interface.c | 42 cs->waiting = 1; in if_lock() 45 cs->waiting = 0; in if_lock() 50 wait_event(cs->waitqueue, !cs->waiting); in if_lock() 76 cs->waiting = 1; in if_version() 79 cs->waiting = 0; in if_version() 84 wait_event(cs->waitqueue, !cs->waiting); in if_version()
|
D | ev-layer.c | 922 cs->waiting = 0; in do_start() 942 cs->waiting = 0; in finish_shutdown() 1119 at_state->waiting = 1; in do_action() 1466 cs->waiting = 0; in do_action() 1478 cs->waiting = 0; in do_action() 1498 cs->waiting = 0; in do_action() 1574 if (at_state->waiting) in process_event() 1619 at_state->waiting = 0; in process_event()
|
D | gigaset.h | 335 int waiting; member 416 int waiting; member
|
/linux-4.4.14/drivers/media/v4l2-core/ |
D | v4l2-async.c | 67 list_for_each_entry(asd, ¬ifier->waiting, list) { in v4l2_async_belongs() 122 if (list_empty(¬ifier->waiting) && notifier->complete) in v4l2_async_test_notify() 148 INIT_LIST_HEAD(¬ifier->waiting); in v4l2_async_notifier_register() 166 list_add_tail(&asd->list, ¬ifier->waiting); in v4l2_async_notifier_register() 318 list_add(&sd->asd->list, ¬ifier->waiting); in v4l2_async_unregister_subdev()
|
/linux-4.4.14/drivers/scsi/ |
D | ppa.c | 40 wait_queue_head_t *waiting; member 60 wake_up(dev->waiting); in got_it() 991 DECLARE_WAIT_QUEUE_HEAD_ONSTACK(waiting); in __ppa_attach() 1004 init_waitqueue_head(&waiting); in __ppa_attach() 1015 dev->waiting = &waiting; in __ppa_attach() 1016 prepare_to_wait(&waiting, &wait, TASK_UNINTERRUPTIBLE); in __ppa_attach() 1024 dev->waiting = NULL; in __ppa_attach() 1025 finish_wait(&waiting, &wait); in __ppa_attach() 1028 dev->waiting = NULL; in __ppa_attach() 1029 finish_wait(&waiting, &wait); in __ppa_attach()
|
D | imm.c | 46 wait_queue_head_t *waiting; member 69 wake_up(dev->waiting); in got_it() 1127 DECLARE_WAIT_QUEUE_HEAD_ONSTACK(waiting); in __imm_attach() 1133 init_waitqueue_head(&waiting); in __imm_attach() 1155 dev->waiting = &waiting; in __imm_attach() 1156 prepare_to_wait(&waiting, &wait, TASK_UNINTERRUPTIBLE); in __imm_attach() 1164 dev->waiting = NULL; in __imm_attach() 1165 finish_wait(&waiting, &wait); in __imm_attach() 1168 dev->waiting = NULL; in __imm_attach() 1169 finish_wait(&waiting, &wait); in __imm_attach()
|
D | st.h | 31 struct completion *waiting; member
|
D | osst.h | 637 struct completion *waiting; member
|
D | st.c | 526 if (SRpnt->waiting) in st_scsi_execute_end() 527 complete(SRpnt->waiting); in st_scsi_execute_end() 594 struct completion *waiting; in st_do_scsi() local 620 waiting = &STp->wait; in st_do_scsi() 621 init_completion(waiting); in st_do_scsi() 622 SRpnt->waiting = waiting; in st_do_scsi() 647 wait_for_completion(waiting); in st_do_scsi() 648 SRpnt->waiting = NULL; in st_do_scsi() 682 SRpnt->waiting = NULL; in write_behind_check()
|
D | hpsa_cmd.h | 429 struct completion *waiting; member
|
D | osst.c | 333 if (SRpnt->waiting) in osst_end_async() 334 complete(SRpnt->waiting); in osst_end_async() 435 struct completion *waiting; in osst_do_scsi() local 467 waiting = &STp->wait; in osst_do_scsi() 468 init_completion(waiting); in osst_do_scsi() 469 SRpnt->waiting = waiting; in osst_do_scsi() 489 wait_for_completion(waiting); in osst_do_scsi() 490 SRpnt->waiting = NULL; in osst_do_scsi() 523 STp->buffer->last_SRpnt->waiting = NULL; in osst_write_behind_check()
|
D | hpsa.c | 2634 c->waiting = &wait; in hpsa_scsi_do_simple_cmd_core() 6497 c->waiting = NULL; in hpsa_send_host_reset() 6780 complete(c->waiting); in finish_cmd()
|
/linux-4.4.14/Documentation/ABI/testing/ |
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-4.4.14/block/ |
D | blk-exec.c | 25 struct completion *waiting = rq->end_io_data; in blk_end_sync_rq() local 33 complete(waiting); in blk_end_sync_rq()
|
D | cfq-iosched.c | 479 CFQG_FLAG_FNS(waiting)
|
/linux-4.4.14/tools/perf/util/ |
D | run-command.c | 162 pid_t waiting = waitpid(pid, &status, 0); in wait_or_whine() local 164 if (waiting < 0) { in wait_or_whine() 171 if (waiting != pid) in wait_or_whine()
|
/linux-4.4.14/arch/arm/include/debug/ |
D | samsung.S | 62 @ busy waiting for non fifo 81 @ idle waiting for non fifo
|
/linux-4.4.14/drivers/parport/ |
D | share.c | 756 tmp->waiting = 0; in parport_register_device() 883 par_dev->waiting = 0; in parport_register_dev_model() 1135 if (dev->waiting & 1) { in parport_claim() 1136 dev->waiting = 0; in parport_claim() 1183 if (dev->waiting & 2 || dev->wakeup) { in parport_claim() 1185 if (test_and_set_bit(0, &dev->waiting) == 0) { in parport_claim() 1217 dev->waiting = 2; in parport_claim_or_block() 1236 if (dev->waiting) { in parport_claim_or_block() 1238 !dev->waiting); in parport_claim_or_block() 1259 dev->waiting = 0; in parport_claim_or_block() [all …]
|
/linux-4.4.14/Documentation/scheduler/ |
D | completion.txt | 24 struct completion that tells the waiting threads of execution if they 36 struct completion, the waiting part through a call to one of the variants of 50 providing the wait queue to place tasks on for waiting and the flag for 119 to wait_for_completion() then the waiting side simply will continue 162 while waiting it will return -ERESTARTSYS; 0 otherwise. 191 variants, except for accounting waiting time as waiting on IO, which has 213 a thread starts waiting. This is achieved by the waiter "consuming"
|
D | sched-stats.txt | 52 8) sum of all time spent waiting to run by tasks on this processor (in 147 2) time spent waiting on a runqueue
|
/linux-4.4.14/drivers/sbus/char/ |
D | bbc_i2c.c | 128 bp->waiting = 1; in wait_for_pin() 144 bp->waiting = 0; in wait_for_pin() 277 if (bp->waiting && in bbc_i2c_interrupt() 316 bp->waiting = 0; in attach_one_i2c()
|
D | bbc_i2c.h | 62 volatile int waiting; member
|
/linux-4.4.14/Documentation/block/ |
D | stat.txt | 58 waited on this block device. If there are multiple I/O requests waiting, 80 on this block device. If there are multiple I/O requests waiting, this 82 number of requests waiting (see "read ticks" above for an example).
|
D | request.txt | 79 struct completion *waiting D Can be used by driver to get signalled
|
D | cfq-iosched.txt | 225 Idling on a queue is primarily about waiting for the next request to come 246 of queues or the tree. So if there are 4 queues waiting for IO to dispatch
|
D | biodoc.txt | 1026 the queue gets explicitly unplugged as part of waiting for completion on that
|
/linux-4.4.14/arch/x86/platform/uv/ |
D | uv_nmi.c | 303 int last_k = 0, waiting = 0; in uv_nmi_wait_cpus() local 329 waiting = 0; in uv_nmi_wait_cpus() 330 } else if (++waiting > uv_nmi_wait_count) in uv_nmi_wait_cpus() 334 if (waiting && (n - k) == 1 && in uv_nmi_wait_cpus()
|
/linux-4.4.14/kernel/locking/ |
D | rwsem-xadd.c | 440 bool waiting = true; /* any queued threads before us */ in rwsem_down_write_failed() local 461 waiting = false; in rwsem_down_write_failed() 466 if (waiting) { in rwsem_down_write_failed()
|
/linux-4.4.14/drivers/gpu/drm/savage/ |
D | savage_state.c | 50 dev_priv->waiting = 1; in savage_emit_clip_rect_s3d() 76 dev_priv->waiting = 1; in savage_emit_clip_rect_s4() 253 dev_priv->waiting = 1; in savage_dispatch_state() 359 if (S3_SAVAGE3D_SERIES(dev_priv->chipset) && dev_priv->waiting) { in savage_dispatch_dma_prim() 368 dev_priv->waiting = 0; in savage_dispatch_dma_prim() 609 if (S3_SAVAGE3D_SERIES(dev_priv->chipset) && dev_priv->waiting) { in savage_dispatch_dma_idx() 618 dev_priv->waiting = 0; in savage_dispatch_dma_idx() 1039 dev_priv->waiting = 1; in savage_bci_cmdbuf()
|
D | savage_drv.h | 186 unsigned int waiting; member
|
/linux-4.4.14/Documentation/accounting/ |
D | taskstats-struct.txt | 100 /* Delay waiting for cpu, while runnable 108 /* Delay waiting for synchronous block I/O to complete 114 /* Delay waiting for page fault I/O (swap in only) */ 177 /* Delay waiting for memory reclaim */
|
D | delay-accounting.txt | 11 a) waiting for a CPU (while being runnable) 49 experienced by the task waiting for the corresponding resource
|
/linux-4.4.14/drivers/block/drbd/ |
D | drbd_interval.h | 13 int waiting:1; /* someone is waiting for this to complete */ member
|
D | drbd_req.c | 70 req->i.waiting = false; in drbd_req_new() 93 if (i->waiting) in drbd_remove_request_interval() 305 if (req->i.waiting) in drbd_req_complete() 530 if (req->i.waiting) in mod_rq_state() 810 if (req->i.waiting) in __req_mod() 990 i->waiting = true; in complete_conflicting_writes()
|
D | drbd_main.c | 3736 i->waiting = true; in drbd_wait_misc()
|
D | drbd_receiver.c | 1489 if (i->waiting) in drbd_remove_epoch_entry_interval()
|
/linux-4.4.14/include/media/ |
D | v4l2-async.h | 82 struct list_head waiting; member
|
/linux-4.4.14/Documentation/ |
D | robust-futex-ABI.txt | 22 call, and handles contested locking by maintaining a list of waiting 24 waiting on a particular futex, and waking up the next waiter on a 32 waiting on the same locks. 80 waiting for a lock on a threads exit if that next thread used the futex 88 indicating their holder died, and wakeup the next thread waiting for 164 they were waiting, and bit 30 is set by the kernel to indicate that the
|
D | futex-requeue-pi.txt | 16 pthread_cond_broadcast() must resort to waking all the tasks waiting 89 is necessary for both the requeue code, as well as the waiting code, 112 possibly wake the waiting tasks. Internally, this system call is
|
D | volatile-considered-harmful.txt | 34 want to play with that data will be waiting on the lock. The spinlock 59 when the processor is busy-waiting on the value of a variable. The right 68 waiting is generally an anti-social act to begin with.
|
D | kselftest.txt | 7 On some systems, hot-plug tests could hang forever waiting for cpu and
|
D | hwspinlock.txt | 70 waiting for it to be released, but give up when the timeout elapses. 82 waiting for it to be released, but give up when the timeout elapses. 94 waiting for it to be released, but give up when the timeout elapses.
|
D | rpmsg.txt | 121 return -ENOMEM without waiting until one becomes available. 135 return -ENOMEM without waiting until one becomes available. 150 return -ENOMEM without waiting until one becomes available.
|
D | md-cluster.txt | 90 or other events that happened while waiting for the TOKEN may have made
|
D | parport.txt | 174 spintime The number of microseconds to busy-loop while waiting
|
D | crc32.txt | 164 immediately, without waiting for the previous loop iteration.
|
D | parport-lowlevel.txt | 595 1 timed out while waiting (35ms elapsed) 621 1 timed out while waiting (usec microseconds have elapsed)
|
D | workqueue.txt | 150 pressure. Else it is possible that the worker-pool deadlocks waiting
|
D | memory-barriers.txt | 1831 signal whilst asleep waiting for the lock to become available. Failed 1946 interaction between two pieces of data: the task state of the task waiting for 2227 Consider, for example, the R/W semaphore slow path. Here a waiting process is 2229 the semaphore's list of waiting processes:
|
D | md.txt | 294 clean, but writes are blocked waiting for 'active' to be written.
|
D | devices.txt | 3327 Under no circumstances should an application hold a lock while waiting
|
D | kernel-parameters.txt | 2629 waiting for the ACK, so if this is set too high
|
/linux-4.4.14/arch/arm/mach-pxa/ |
D | sleep.S | 33 20: b 20b @ waiting for sleep 171 20: b 20b @ loop waiting for sleep
|
/linux-4.4.14/drivers/gpu/drm/nouveau/include/nvkm/subdev/ |
D | clk.h | 85 atomic_t waiting; member
|
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/subdev/clk/ |
D | base.c | 210 if (!atomic_xchg(&clk->waiting, 0)) in nvkm_pstate_work() 243 atomic_set(&clk->waiting, 1); in nvkm_pstate_calc() 246 wait_event(clk->wait, !atomic_read(&clk->waiting)); in nvkm_pstate_calc() 572 atomic_set(&clk->waiting, 0); in nvkm_clk_ctor()
|
/linux-4.4.14/drivers/net/ethernet/cavium/liquidio/ |
D | octeon_console.c | 450 console->waiting = 0; in octeon_console_handle_result() 511 if (console->waiting) { in check_console() 591 console->waiting = 0; in octeon_add_console()
|
D | octeon_device.h | 181 u32 waiting; member
|
/linux-4.4.14/drivers/gpu/drm/ |
D | drm_dma.c | 133 buf->waiting = 0; in drm_legacy_free_buffer()
|
D | drm_bufs.c | 700 buf->waiting = 0; in drm_legacy_addbufs_agp() 898 buf->waiting = 0; in drm_legacy_addbufs_pci() 1063 buf->waiting = 0; in drm_legacy_addbufs_sg()
|
/linux-4.4.14/arch/cris/ |
D | Kconfig.debug | 23 didn't before). The kernel halts when it boots, waiting for gdb if
|
/linux-4.4.14/Documentation/networking/ |
D | spider_net.txt | 29 and is waiting to be emptied and processed by the OS. A "not-in-use" 132 which, from the OS point of view, is empty; the OS will be waiting for 135 is a potential deadlock, with the OS waiting for one descr to fill, 136 while the hardware is waiting for a different set of descrs to become 158 as explained in the last section. The OS is waiting for descr 255 to
|
D | mac80211-injection.txt | 28 IEEE80211_RADIOTAP_F_TX_NOACK: frame should be sent without waiting for
|
D | operstates.txt | 61 Interface is L1 up, but waiting for an external event, f.e. for a 157 waiting for operstate to go IF_OPER_UP/IF_OPER_UNKNOWN before
|
D | tcp-thin.txt | 13 waiting for long timeouts.
|
D | cxacru.txt | 65 "waiting"
|
D | driver.txt | 72 This error can deadlock sockets waiting for send buffer room
|
D | netdevices.txt | 104 NAPI_STATE_SCHED napi->state bit, waiting for all pending
|
D | batman-adv.txt | 28 The module is now waiting for activation. You must add some in-
|
D | PLIP.txt | 74 the PLIP driver would constantly poll the parallel port for data waiting,
|
D | pktgen.txt | 42 the TX ring might just be waiting for cleanup.
|
D | rds.txt | 223 Messages waiting in the receive queue on the receiving socket
|
D | phy.txt | 48 time, so it is safe for them to block, waiting for an interrupt to signal
|
D | rxrpc.txt | 250 Any messages waiting in the receive queue for that call will be discarded. 662 Any packets waiting in the socket's receive queue will be discarded if
|
D | timestamping.txt | 325 block waiting on a timestamp, use poll or select. poll() will return
|
D | ip-sysctl.txt | 211 packet for the flow is waiting in Qdisc queues or device transmit
|
D | bonding.txt | 2518 case). If there are slave interfaces waiting for the updelay timeout
|
/linux-4.4.14/Documentation/RCU/ |
D | trace.txt | 136 grace-period processing that they are in (new, waiting for 137 grace period to start, waiting for grace period to end, ready 152 waiting on the current grace period. 156 thus waiting to be invoked. Note that callbacks in 214 "W" The kernel thread is waiting because there is no work 217 "O" The kernel thread is waiting because it has been 400 o "qsp" is the number of times that the RCU was waiting for a 471 "W" The kernel thread is waiting because there is no work 535 o "qlen" is the number of RCU callbacks currently waiting either 536 for an RCU grace period or waiting to be invoked. This is the
|
D | rcubarrier.txt | 73 We instead need the rcu_barrier() primitive. Rather than waiting for 78 without waiting for a grace period to elapse.
|
D | checklist.txt | 246 those waiting for a grace period to elapse. Enforce a
|
D | whatisRCU.txt | 1014 short of memory). In contrast, if blocking waiting
|
D | RTFP.txt | 70 simplest deferred-free technique: simply waiting a fixed amount of time
|
/linux-4.4.14/include/drm/ |
D | drm_legacy.h | 57 __volatile__ int waiting; /**< On kernel DMA queue */ member
|
/linux-4.4.14/drivers/mmc/host/ |
D | jz4740_mmc.c | 136 unsigned long waiting; member 431 set_bit(0, &host->waiting); in jz4740_mmc_poll_irq() 599 if (!test_and_clear_bit(0, &host->waiting)) in jz4740_mmc_timeout() 797 if (test_and_clear_bit(0, &host->waiting)) { in jz_mmc_irq() 854 set_bit(0, &host->waiting); in jz4740_mmc_request()
|
/linux-4.4.14/drivers/net/wan/ |
D | sdla.c | 437 int ret, waiting, len; in sdla_cmd() local 461 waiting = 1; in sdla_cmd() 463 while (waiting && time_before_eq(jiffies, jiffs)) in sdla_cmd() 465 if (waiting++ % 3) in sdla_cmd() 469 waiting = ((volatile int)(cmd_buf->opp_flag)); in sdla_cmd() 474 if (!waiting) in sdla_cmd()
|
/linux-4.4.14/Documentation/locking/ |
D | lockstat.txt | 49 total - total time we spend waiting on this lock 50 avg - average time spent waiting on this lock
|
D | mutex-design.txt | 72 waiting to spin on mutex owner, only to go directly to slowpath upon 82 task and busy-waiting for a few cycles instead of immediately sleeping,
|
D | rt-mutex-design.txt | 39 Now there's no way of knowing how long A will be sleeping waiting for C 104 waiter is sometimes used in reference to the task that is waiting 109 top waiter - The highest priority process waiting on a specific mutex. 111 top pi waiter - The highest priority process waiting on one of the mutexes 223 is waiting on a mutex that is owned by the task. So if the task has 372 task's own normal priority, or if a process of a higher priority is waiting on 396 always contains the highest priority task that is waiting on a mutex owned 448 task that owns a mutex that this current task is waiting on. A priority chain 673 priority process currently waiting on this mutex, then we remove the
|
D | spinlocks.txt | 123 lock will obviously never be released (because the interrupt is waiting
|
D | ww-mutex-design.txt | 14 become ready. If you think about this in terms of waiting on a buffer
|
/linux-4.4.14/Documentation/devicetree/bindings/clock/ti/ |
D | interface.txt | 18 capability for waiting clock to be ready
|
/linux-4.4.14/Documentation/usb/ |
D | dwc3.txt | 39 handles the remaining EP work which might sleep such as waiting
|
/linux-4.4.14/drivers/block/ |
D | cciss_cmd.h | 210 struct completion *waiting; member
|
D | cciss.c | 1544 c->waiting = &wait; in cciss_passthru() 1672 c->waiting = &wait; in cciss_bigpassthru() 2700 c->waiting = NULL; in cciss_send_reset() 2806 c->waiting = &wait; in sendcmd_withirq_core() 3494 complete(c->waiting); in finish_cmd()
|
D | cciss_scsi.c | 944 c->waiting = &wait; in cciss_scsi_do_simple_cmd()
|
/linux-4.4.14/arch/arm/mach-sa1100/ |
D | sleep.S | 143 20: b 20b @ loop waiting for sleep
|
/linux-4.4.14/drivers/scsi/libsas/ |
D | sas_ata.c | 590 struct completion *waiting; in sas_ata_task_abort() local 607 waiting = qc->private_data; in sas_ata_task_abort() 608 complete(waiting); in sas_ata_task_abort()
|
/linux-4.4.14/Documentation/filesystems/ |
D | fuse.txt | 133 'waiting' 135 The number of requests which are waiting to be transferred to 137 no filesystem activity and 'waiting' is non-zero, then the 143 connection. This means that all waiting requests will be aborted an
|
D | ocfs2.txt | 103 journal_async_commit Commit block can be written to disk without waiting
|
D | directory-locking | 79 waiting on another non-directory lock with a larger address. Therefore
|
D | xfs-delayed-logging-design.txt | 462 complete before waiting on the one we need to complete. We do this 525 available when required, then the regrant code will sleep waiting for it. 554 a CIL push triggered by a log force, only that there is no waiting for the 666 checkpoints and needs to block waiting for checkpoints to complete their commit 672 events they are waiting for are different. The checkpoint commit record
|
D | proc.txt | 323 blkio_ticks time spent waiting for block IO 896 Dirty: Memory which is waiting to get written back to the disk 1299 - iowait: waiting for I/O to complete 1325 waiting for I/O to complete.
|
D | coda.txt | 231 when no messages are waiting or being processed. 364 file descriptor for the device. The process P is kept waiting on an 372 message arrival. The process P is kept waiting on a KernelEvent
|
D | spufs.txt | 338 0x08 SPU is waiting for a channel.
|
D | path-lookup.txt | 114 new list before waiting for a grace period, this can result in a concurrent RCU
|
D | ext4.txt | 142 journal_async_commit Commit block can be written to disk without waiting
|
D | vfs.txt | 539 complete. While waiting ->sync_page (if defined) will be called on 1048 waiting to explore behind a 'mountpoint' whilst letting the daemon go
|
/linux-4.4.14/Documentation/i2c/ |
D | i2c-stub | 59 If your target driver polls some byte or word waiting for it to change, the
|
/linux-4.4.14/Documentation/sysctl/ |
D | net.txt | 71 Approximate time in us to busy loop waiting for packets on the device queue. 82 Approximate time in us to busy loop waiting for events. 239 received queue (bytes waiting for applications to read) the state and the uid
|
D | kernel.txt | 234 parallel, but that no waiting will take place (i.e. the collecting
|
/linux-4.4.14/Documentation/cgroups/ |
D | blkio-controller.txt | 225 - Total amount of time the IOs for this cgroup spent waiting in the 228 measure of total time the cgroup spent waiting but rather a measure of 230 this metric does not include the time spent waiting for service once 261 waiting in the scheduler queue. This is in nanoseconds. If this is 262 read when the cgroup is in a waiting (for timeslice) state, the stat
|
D | freezer-subsystem.txt | 22 blocked, or ignored it can be seen by waiting or ptracing parent tasks.
|
D | cpusets.txt | 532 CPU Y without waiting task A on CPU X. 548 on the next tick. For some applications in special situation, waiting
|
D | memory.txt | 496 dirty - # of bytes that are waiting to get written back to the disk.
|
/linux-4.4.14/Documentation/scsi/ |
D | st.txt | 97 skip waiting. 175 2. io_ns - The amount of time spent waiting (in nanoseconds) for all I/O 184 6. read_ns - The amount of time (in nanoseconds) spent waiting for read 188 9. write_ns - The amount of time (in nanoseconds) spent waiting for write 577 the driver is waiting. With the command 'ps -l' you can see the state 579 waiting for something. The field WCHAN tells where the driver is 580 waiting. If you have the current System.map in the correct place (in
|
D | ChangeLog.sym53c8xx_2 | 118 threads. A timer is also used to prevent from waiting indefinitely.
|
D | ChangeLog.1992-1997 | 167 * st.c: Perform some waiting operations with interrupts off. 502 Do not use waiting loops - use up and down mechanism as long 551 all been waiting for. It fixes a problem whereby the driver 832 processes waiting. 1235 * (Throughout): Use request.sem instead of request.waiting. 1980 (allocate_request, request_queueable): Init request.waiting to NULL if
|
D | ChangeLog.ncr53c8xx | 443 inserting these commands into the waiting list. The waiting list
|
D | ChangeLog.megaraid_sas | 437 waiting for depending on cmd completion from isr path.
|
D | ChangeLog.megaraid | 426 ii. Display elapsed time (countdown) while waiting for FW to boot.
|
D | ChangeLog.lpfc | 29 if we timed out waiting for command to complete after abort was 390 waiting on a semaphore and "modprobe -r lpfc" is not always
|
/linux-4.4.14/Documentation/vm/ |
D | page_migration | 135 so will enable access for user space processes not already waiting for 139 Processes waiting on the page lock will redo their page faults
|
D | userfaultfd.txt | 97 aren't waiting for userfaults (i.e. network bound) can keep running in
|
/linux-4.4.14/fs/squashfs/ |
D | Kconfig | 78 machines due to waiting on decompressor availability. 92 machines due to waiting on decompressor availability.
|
/linux-4.4.14/Documentation/device-mapper/ |
D | dm-io.txt | 70 always available in order to avoid unnecessary waiting while performing I/O.
|
D | log-writes.txt | 19 make it easier to detect improper waiting/flushing.
|
D | cache-policies.txt | 34 waiting for the cache and another two for those in the cache (a set for
|
/linux-4.4.14/drivers/staging/lustre/lustre/osc/ |
D | osc_cache.c | 2624 struct osc_extent *waiting = NULL; in osc_cache_truncate_start() local 2652 waiting = osc_extent_get(ext); in osc_cache_truncate_start() 2721 if (waiting != NULL) { in osc_cache_truncate_start() 2726 rc = osc_extent_wait(env, waiting, OES_INV); in osc_cache_truncate_start() 2728 OSC_EXTENT_DUMP(D_CACHE, waiting, "error: %d.\n", rc); in osc_cache_truncate_start() 2730 osc_extent_put(env, waiting); in osc_cache_truncate_start() 2731 waiting = NULL; in osc_cache_truncate_start()
|
/linux-4.4.14/net/irda/ |
D | Kconfig | 75 start backing-off before sending another RR frame, waiting longer
|
/linux-4.4.14/Documentation/x86/x86_64/ |
D | machinecheck | 74 exception. 0 to disable waiting for other CPUs.
|
/linux-4.4.14/Documentation/dmaengine/ |
D | dmatest.txt | 51 waiting is disabled.
|
D | provider.txt | 283 transaction descriptor to a pending queue, waiting
|
/linux-4.4.14/Documentation/misc-devices/mei/ |
D | mei-client-bus.txt | 50 In order for drivers to be notified of pending events waiting for them (e.g.
|
/linux-4.4.14/drivers/scsi/aic7xxx/ |
D | aic79xx.seq | 85 * If we have completions stalled waiting for the qfreeze 249 * If there are more commands waiting to be dma'ed 259 * bother waiting for another command to complete. 364 * into the waiting for selection queue. Otherwise 369 * SCB can be queued to the waiting for selection 400 * Append SCB to the tail of the waiting for 420 * a MK_MESSAGE SCB waiting to enter the queue. 656 * Dequeue all SCBs sent from the waiting queue 657 * Requeue all SCBs *not* sent to the tail of the waiting queue 751 * Requeue any SCBs not sent, to the tail of the waiting Q. [all …]
|
D | aic7xxx.seq | 51 * A few words on the waiting SCB list: 59 * create yet another SCB waiting for selection. The solution used here is to 147 * Start the first entry on the waiting SCB list. 429 * After the selection, remove this SCB from the "waiting SCB"
|
D | aic79xx.reg | 4049 * the waiting for selection list until the
|
/linux-4.4.14/drivers/infiniband/hw/nes/ |
D | nes_verbs.c | 114 cqp_request->waiting = 1; in nes_alloc_mw() 177 cqp_request->waiting = 1; in nes_dealloc_mw() 307 cqp_request->waiting = 1; in alloc_fast_reg_mr() 1322 cqp_request->waiting = 1; in nes_create_qp() 1640 cqp_request->waiting = 1; in nes_create_cq() 1799 cqp_request->waiting = 1; in nes_destroy_cq() 1937 cqp_request->waiting = 1; in nes_reg_mr() 2676 cqp_request->waiting = 1; in nes_dereg_mr() 2860 cqp_request->waiting = 1; in nes_hw_modify_qp() 2862 cqp_request->waiting = 0; in nes_hw_modify_qp()
|
D | nes_utils.c | 585 cqp_request->waiting = 0; in nes_get_cqp_request() 658 cqp_request->waiting, atomic_read(&cqp_request->refcount)); in nes_post_cqp_request()
|
D | nes_hw.c | 3057 if (cqp_request->waiting) { in nes_cqp_ce_handler() 3788 cqp_request->waiting = 1; in nes_manage_apbvt() 3848 cqp_request->waiting = 0; in nes_manage_arp_cache() 3896 cqp_request->waiting = 1; in flush_wqes() 3899 cqp_request->waiting = 0; in flush_wqes()
|
D | nes_hw.h | 889 u8 waiting; member
|
D | nes.c | 337 cqp_request->waiting = 0; in nes_rem_ref()
|
/linux-4.4.14/Documentation/video4linux/ |
D | videobuf | 310 waiting for it. 314 - Mark the buffer as done and wake up the process waiting for it. 323 process is waiting on it. That test can be done by examining the buffer's
|
D | v4l2-framework.txt | 736 processes to access the device node while the first process is waiting for
|
/linux-4.4.14/include/linux/ |
D | parport.h | 156 unsigned long waiting; /* long req'd for set_bit --RR */ member
|
/linux-4.4.14/arch/mn10300/kernel/ |
D | head.S | 400 # now sleep waiting for further instructions
|
/linux-4.4.14/Documentation/filesystems/pohmelfs/ |
D | design_notes.txt | 44 caller sleeps waiting for it. Thus, it is possible to issue multiple read commands to different
|
/linux-4.4.14/Documentation/powerpc/ |
D | firmware-assisted-dump.txt | 98 we check to see if an active dump is waiting for us. If yes 106 If there is no waiting dump data, then only the memory required
|
/linux-4.4.14/Documentation/filesystems/caching/ |
D | object.txt | 247 Any child objects waiting on this one are given CPU time so that they too 253 The object comes to this state if it was waiting on its parent in
|
D | operations.txt | 174 necessary (the object might have died whilst the thread was waiting).
|
D | netfs-api.txt | 580 anyone waiting for that bit will be woken up.
|
/linux-4.4.14/drivers/char/ipmi/ |
D | ipmi_ssif.c | 556 bool waiting; in retry_timeout() local 562 waiting = ssif_info->waiting_alert; in retry_timeout() 566 if (waiting) in retry_timeout()
|
/linux-4.4.14/fs/fuse/ |
D | cuse.c | 576 static DEVICE_ATTR(waiting, 0400, cuse_class_waiting_show, NULL);
|
/linux-4.4.14/Documentation/arm/ |
D | tcm.txt | 55 the CPU and then we hang inside ITCM waiting for an
|
/linux-4.4.14/Documentation/PCI/ |
D | pci-error-recovery.txt | 33 waiting for some i/o-space register to change, when it never will. 131 a chance to cleanup, waiting for pending stuff (timers, whatever, etc...) 169 >>> recovery implementation (e.g. waiting for all notification threads
|
/linux-4.4.14/Documentation/aoe/ |
D | aoe.txt | 43 "cat /dev/etherd/err" blocks, waiting for error diagnostic output,
|
/linux-4.4.14/Documentation/input/ |
D | ntrig.txt | 90 contact immediately overrides the waiting period and leads to activation.
|
/linux-4.4.14/Documentation/nfc/ |
D | nfc-hci.txt | 21 context blocks waiting for response) or asynchronously (the response is returned 233 waiting command execution. Response processing involves invoking the completion
|
/linux-4.4.14/fs/exofs/ |
D | ore.c | 340 struct completion *waiting = p; in _sync_done() local 342 complete(waiting); in _sync_done()
|
/linux-4.4.14/Documentation/power/ |
D | suspend-and-interrupts.txt | 98 system sleep state that works by idling all of the processors and waiting for
|
D | suspend-and-cpuhotplug.txt | 268 it will now start waiting on the frozen userspace in the
|
D | freezing-of-tasks.txt | 138 user threads and then waiting for a sync is practically one of the easier
|
/linux-4.4.14/drivers/lightnvm/ |
D | rrpc.c | 250 struct completion *waiting = bio->bi_private; in rrpc_end_sync_bio() local 255 complete(waiting); in rrpc_end_sync_bio()
|
/linux-4.4.14/Documentation/isdn/ |
D | README.hysdn | 132 1007 Timeout waiting for card ready during boot
|
D | INTERFACE | 504 If ICALLW is signalled the incoming call is a waiting call without
|
/linux-4.4.14/drivers/gpu/drm/i915/ |
D | i915_gpu_error.c | 301 err_printf(m, " waiting: %s\n", yesno(ring->waiting)); in i915_ring_error_state() 892 ering->waiting = waitqueue_active(&ring->irq_queue); in i915_record_ring_state()
|
D | i915_drv.h | 529 bool waiting; member
|
/linux-4.4.14/drivers/scsi/lpfc/ |
D | lpfc_bsg.c | 61 int waiting; member 1255 evt->waiting = 1; in lpfc_bsg_hba_set_event() 2631 evt->waiting = 1; in lpfcdiag_loop_get_xri() 2647 evt->waiting = 0; in lpfcdiag_loop_get_xri() 3209 evt->waiting = 1; in lpfc_bsg_diag_loopback_run() 3214 evt->waiting = 0; in lpfc_bsg_diag_loopback_run()
|
/linux-4.4.14/Documentation/arm/SA1100/ |
D | Assabet | 237 Then, rebooting the Assabet is just a matter of waiting for the login prompt.
|
/linux-4.4.14/drivers/scsi/csiostor/ |
D | csio_hw.c | 873 int waiting = FW_CMD_HELLO_TIMEOUT; in csio_do_hello() local 888 waiting -= 50; in csio_do_hello() 898 if (waiting <= 0) { in csio_do_hello()
|
/linux-4.4.14/Documentation/filesystems/nfs/ |
D | rpc-cache.txt | 156 select or poll for read will block waiting for another request to be
|
/linux-4.4.14/Documentation/hwmon/ |
D | lm90 | 269 two transactions will typically mean twice as much delay waiting for
|
/linux-4.4.14/Documentation/virtual/kvm/ |
D | msr.txt | 192 up all processes waiting for APFs and no individual type 2 APFs
|
D | api.txt | 1052 is waiting for an interrupt [x86]
|
/linux-4.4.14/net/netfilter/ipvs/ |
D | Kconfig | 246 the idle server, instead of waiting for a fast one. When there
|
/linux-4.4.14/arch/powerpc/xmon/ |
D | xmon.c | 445 goto waiting; in xmon_core() 475 waiting: in xmon_core()
|
/linux-4.4.14/Documentation/target/ |
D | tcmu-design.txt | 137 cmd_tail, the ring is empty -- no commands are currently waiting to be
|
/linux-4.4.14/Documentation/gpio/ |
D | consumer.txt | 198 SPI. Commands to read or write those GPIO values require waiting to get to the
|
D | gpio-legacy.txt | 198 or SPI. Commands to read or write those GPIO values require waiting to
|
/linux-4.4.14/scripts/ |
D | spelling.txt | 1056 wating||waiting
|
/linux-4.4.14/Documentation/hid/ |
D | hid-transport.txt | 77 not perform any synchronous operations like waiting for acknowledgements or
|
/linux-4.4.14/Documentation/rapidio/ |
D | rapidio.txt | 129 and are waiting for enumeration to be completed.
|
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/engine/ce/fuc/ |
D | com.fuc | 262 // is there a channel waiting to be loaded?
|
/linux-4.4.14/drivers/net/ethernet/chelsio/cxgb4/ |
D | t4_hw.c | 5817 int waiting = FW_CMD_HELLO_TIMEOUT; in t4_fw_hello() local 5830 waiting -= 50; in t4_fw_hello() 5840 if (waiting <= 0) { in t4_fw_hello()
|
/linux-4.4.14/drivers/block/mtip32xx/ |
D | mtip32xx.c | 579 struct completion *waiting = command->comp_data; in mtip_completion() local 586 complete(waiting); in mtip_completion()
|
/linux-4.4.14/net/sched/ |
D | Kconfig | 51 scheduling algorithm. This algorithm classifies the waiting packets
|
/linux-4.4.14/drivers/ata/ |
D | libata-core.c | 1526 struct completion *waiting = qc->private_data; in ata_qc_complete_internal() local 1528 complete(waiting); in ata_qc_complete_internal()
|
/linux-4.4.14/Documentation/development-process/ |
D | 2.Process | 94 worse; the pile of changes waiting for the next merge window will grow
|
/linux-4.4.14/arch/arm/mm/ |
D | Kconfig | 953 drain and waiting for all buffers empty.
|
/linux-4.4.14/init/ |
D | Kconfig | 440 Collect information on time spent by a task waiting for system 1878 without waiting for anyone to stop using it (using the -f option to
|
/linux-4.4.14/Documentation/filesystems/cifs/ |
D | CHANGES | 440 waiting on an SMB response) in SendReceive when session dies but
|
/linux-4.4.14/Documentation/cdrom/ |
D | cdrom-standard.tex | 343 course waiting for the device should not use processor time.
|
/linux-4.4.14/arch/arm/ |
D | Kconfig | 1187 continuously polls a memory location waiting to observe an update.
|
/linux-4.4.14/Documentation/sound/alsa/ |
D | ALSA-Configuration.txt | 1814 sleep_interval - How long to sleep when waiting for reply
|
/linux-4.4.14/Documentation/virtual/uml/ |
D | UserModeLinux-HOWTO.txt | 721 appear to hang. In reality, it's waiting for a telnet to connect, at
|