| /linux-4.4.14/Documentation/ABI/obsolete/ |
| D | sysfs-class-rfkill | 10 This file is deprecated and scheduled to be removed in 2014,
28 This file is scheduled to be removed in 2012.
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | pmu-ebb.txt | 43 user process. This means once an EBB event is scheduled on the PMU, no non-EBB
55 first will be scheduled and the other will be put in error state. See the
83 userspace is able to reliably determine which PMC the event is scheduled on.
94 guarantee that it has been scheduled on the PMU. To ensure that the EBB event
95 has been scheduled on the PMU, you must perform a read() on the event. If the
96 read() returns EOF, then the event has not been scheduled and EBBs are not
|
| /linux-4.4.14/kernel/ |
| D | workqueue_internal.h | 33 struct list_head scheduled; /* L: scheduled works */ member
|
| D | workqueue.c | 1646 INIT_LIST_HEAD(&worker->scheduled); in alloc_worker()
1795 WARN_ON(!list_empty(&worker->scheduled)) || in destroy_worker()
2023 move_linked_works(work, &collision->scheduled, NULL); in process_one_work()
2126 while (!list_empty(&worker->scheduled)) { in process_scheduled_works()
2127 struct work_struct *work = list_first_entry(&worker->scheduled, in process_scheduled_works()
2183 WARN_ON_ONCE(!list_empty(&worker->scheduled)); in worker_thread()
2202 if (unlikely(!list_empty(&worker->scheduled))) in worker_thread()
2205 move_linked_works(work, &worker->scheduled, NULL); in worker_thread()
2251 struct list_head *scheduled = &rescuer->scheduled; in rescuer_thread() local
2297 WARN_ON_ONCE(!list_empty(scheduled)); in rescuer_thread()
[all …]
|
| /linux-4.4.14/Documentation/ABI/removed/ |
| D | devfs | 2 Date: July 2005 (scheduled), finally removed in kernel v2.6.18
|
| D | dv1394 | 2 Date: May 2010 (scheduled), finally removed in kernel v2.6.37
|
| D | raw1394 | 2 Date: May 2010 (scheduled), finally removed in kernel v2.6.37
|
| D | video1394 | 2 Date: May 2010 (scheduled), finally removed in kernel v2.6.37
|
| /linux-4.4.14/Documentation/vm/ |
| D | active_mm.txt | 46 anonymous process gets scheduled away, the borrowed address space is
58 gets scheduled away in favour of a real thread, the "zombie" mm gets
|
| /linux-4.4.14/drivers/scsi/libsas/ |
| D | sas_scsi_host.c | 449 int scheduled = 0, tries = 100; in sas_queue_reset() local
459 while (!scheduled && tries--) { in sas_queue_reset()
463 scheduled = 1; in sas_queue_reset()
476 if (scheduled) in sas_queue_reset()
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-deadline.txt | 53 scheduled using EDF[1] on these scheduling deadlines (the task with the
103 and cannot be scheduled until its scheduling deadline. The "replenishment
195 (Task_1 is scheduled as soon as it is released, and finishes just in time
196 to respect its deadline; Task_2 is scheduled immediately after Task_1, hence
234 result, Task_1 can be scheduled only at time t + e, and will finish at
278 In order to do this, a task must be scheduled by setting:
398 runtime at each instance, and that is scheduled according to the urgency of
496 The above creates 2 threads. The first one, scheduled by SCHED_DEADLINE,
497 executes for 10ms every 100ms. The second one, scheduled at SCHED_FIFO
|
| D | sched-domains.txt | 29 through scheduler_tick(). It raises a softirq after the next regularly scheduled
|
| D | sched-rt-group.txt | 69 0.00015s. So this group can be scheduled with a period of 0.005s and a run time
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | pxa_camera.txt | 151 - Videobuffer3 capture is not scheduled on DMA chain (as it stopped !!!)
165 and Videobuffer3 is scheduled on DMA chain.
|
| D | soc-camera.txt | 39 mx1_camera.c (broken, scheduled for removal), mx2_camera.c, mx3_camera.c,
|
| /linux-4.4.14/drivers/rtc/ |
| D | interface.c | 309 time64_t now, scheduled; in __rtc_set_alarm() local
315 scheduled = rtc_tm_to_time64(&alarm->time); in __rtc_set_alarm()
322 if (scheduled <= now) in __rtc_set_alarm()
|
| /linux-4.4.14/Documentation/dmaengine/ |
| D | pxa_dma.txt | 104 is raised. Upon this interrupt, a tasklet is scheduled for the physical
111 be raised, and the tasklet will be scheduled once again, having a new
|
| /linux-4.4.14/lib/ |
| D | Kconfig.kmemcheck | 61 be scheduled. If the queue is full, new error reports will be
|
| /linux-4.4.14/Documentation/block/ |
| D | cfq-iosched.txt | 269 100ms each. If a REQ_NOIDLE request comes in, it will be scheduled
272 request comes in, again it will be scheduled after 1second. Repeat it
281 scheduled for another second. A process doing small fsync, will suffer
|
| D | biodoc.txt | 1022 unplugged (to open up the flow again), either through a scheduled task or
|
| /linux-4.4.14/sound/ |
| D | Kconfig | 48 /proc/devices. sound-slot/service-* module aliases are scheduled
|
| /linux-4.4.14/Documentation/ |
| D | lockup-watchdogs.txt | 50 timestamp every time it is scheduled. If that timestamp is not updated
|
| D | cputopology.txt | 94 online: CPUs that are online and being scheduled [cpu_online_mask]
|
| D | workqueue.txt | 157 functions are deprecated and scheduled for removal. alloc_workqueue()
165 resources, scheduled and executed.
368 1. Something being scheduled in rapid succession
|
| D | rtc.txt | 192 state until it's time to execute some scheduled tasks.
|
| D | kmemcheck.txt | 134 emptied as soon as a tasklet may be scheduled. If the queue is full,
|
| D | devices.txt | 26 The symbol {2.6} means the allocation is obsolete and scheduled for
|
| /linux-4.4.14/drivers/infiniband/hw/qib/ |
| D | qib_verbs.c | 338 int *scheduled) in qib_post_one_send() argument
465 *scheduled = 1; in qib_post_one_send()
484 int scheduled = 0; in qib_post_send() local
487 err = qib_post_one_send(qp, wr, &scheduled); in qib_post_send()
495 if (!scheduled) in qib_post_send()
|
| /linux-4.4.14/Documentation/usb/ |
| D | ehci.txt | 82 limits on the number of periodic transactions that can be scheduled,
210 transfers are fully scheduled, so the main issue is likely to be how
|
| D | error-codes.txt | 41 the URB would be scheduled in have already expired.
|
| D | proc_usb_info.txt | 152 The percentage is how much of the "reserved" bandwidth is scheduled by
|
| D | power-management.txt | 407 the device hasn't been idle for long enough, a timer is scheduled to
|
| /linux-4.4.14/Documentation/networking/ |
| D | operstates.txt | 109 scheduled to translate the flag combination to IFLA_OPERSTATE as
|
| D | stmmac.txt | 55 scheduled to release the transmit resources.
63 Then the poll method will be scheduled at some future point.
|
| /linux-4.4.14/Documentation/nfc/ |
| D | nfc-hci.txt | 221 MSGTXWQ context will then be scheduled and invoke nfc_hci_msg_tx_work().
226 SMW context gets scheduled and invokes nfc_shdlc_sm_work(). This function
|
| /linux-4.4.14/drivers/block/paride/ |
| D | Transition-notes | 2 If ps_tq is scheduled, ps_tq_active is 1. ps_tq_int() can be called
|
| /linux-4.4.14/Documentation/power/ |
| D | runtime_pm.txt | 196 scheduled requests to execute the other callbacks for the same device,
197 except for scheduled autosuspends.
326 not yet expired then an autosuspend is scheduled for the appropriate time
353 hasn't been scheduled (or queued up if 'delay' is 0); if the execution of
354 ->runtime_suspend() is already scheduled and not yet expired, the new
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-devices-system-cpu | 29 online: cpus that are online and being scheduled.
|
| /linux-4.4.14/arch/x86/crypto/ |
| D | sha512-ssse3-asm.S | 259 movdqa %xmm0, W_t(\rnd) # Store scheduled qwords
|
| D | sha256-avx2-asm.S | 651 #### Do second block using previously scheduled results
|
| /linux-4.4.14/arch/cris/arch-v10/kernel/ |
| D | entry.S | 409 ;; process due to a SEGV, scheduled due to a page blocking or
|
| /linux-4.4.14/Documentation/timers/ |
| D | highres.txt | 216 evaluates the next scheduled timer event (from both hrtimers and the timer
|
| /linux-4.4.14/tools/perf/ |
| D | design.txt | 269 A counter group is scheduled onto the CPU as a unit, that is, it will
|
| /linux-4.4.14/Documentation/scsi/ |
| D | scsi_eh.txt | 116 After a timeout occurs a command abort is scheduled from
|
| /linux-4.4.14/Documentation/trace/ |
| D | ftrace.txt | 25 a task is woken to the task is actually scheduled in.
533 the highest priority task to get scheduled after
858 scheduled out as part of the function call.
1510 and in the running state 'R'. The sleep task was scheduled in with
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | cpusets.txt | 114 CPUs a task may be scheduled (sched_setaffinity) and on which Memory
158 displaying the task's cpus_allowed (on which CPUs it may be scheduled)
|
| D | unified-hierarchy.txt | 98 command. Note that this is still under development and scheduled to
|
| /linux-4.4.14/Documentation/s390/ |
| D | cds.txt | 340 or similar needs to be scheduled. During I/O processing the Linux/390 generic
|
| /linux-4.4.14/kernel/trace/ |
| D | Kconfig | 222 to be scheduled in, starting from the point it has woken up.
|
| /linux-4.4.14/Documentation/security/ |
| D | credentials.txt | 540 reference count reaches zero, the credentials will be scheduled for
|
| /linux-4.4.14/net/sched/ |
| D | Kconfig | 53 in turn scheduled by separate algorithms.
|
| /linux-4.4.14/Documentation/DocBook/ |
| D | device-drivers.xml.db | 131 API-flush-scheduled-work
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | kernel.txt | 336 Check interval. When a task in D state did not get scheduled
|
| /linux-4.4.14/net/netfilter/ |
| D | Kconfig | 40 and is also scheduled to replace the old syslog-based ipt_LOG
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | coda.txt | 319 Venus. The process P will be scheduled at some point and continues
|
| D | proc.txt | 320 task_cpu which CPU the task is scheduled on
|