Searched full:scheduled (Results 1 – 25 of 60) sorted by relevance
123
/Documentation/powerpc/ |
D | pmu-ebb.rst | 44 user process. This means once an EBB event is scheduled on the PMU, no non-EBB 56 first will be scheduled and the other will be put in error state. See the 84 userspace is able to reliably determine which PMC the event is scheduled on. 95 guarantee that it has been scheduled on the PMU. To ensure that the EBB event 96 has been scheduled on the PMU, you must perform a read() on the event. If the 97 read() returns EOF, then the event has not been scheduled and EBBs are not
|
/Documentation/ABI/removed/ |
D | devfs | 2 Date: July 2005 (scheduled), finally removed in kernel v2.6.18
|
D | sysfs-class-rfkill | 11 This file was scheduled to be removed in 2012, and was removed
|
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
|
/Documentation/devicetree/bindings/net/ |
D | ti,k3-am654-cpts.yaml | 24 - Ethernet Enhanced Scheduled Traffic Operations (CPTS_ESTFn) (TSN) 29 Scheduled Traffic Operations (CPTS_ESTFn) and PCIe Subsystem Precision Time
|
D | ti,k3-am654-cpsw-nuss.yaml | 35 IEEE 802.1Qbv/D2.2 Enhancements for Scheduled Traffic
|
/Documentation/vm/ |
D | active_mm.rst | 54 anonymous process gets scheduled away, the borrowed address space is 66 gets scheduled away in favour of a real thread, the "zombie" mm gets
|
/Documentation/scheduler/ |
D | sched-deadline.rst | 59 scheduled using EDF[1] on these scheduling deadlines (the task with the 109 and cannot be scheduled until its scheduling deadline. The "replenishment 389 (Task_1 is scheduled as soon as it is released, and finishes just in time 390 to respect its deadline; Task_2 is scheduled immediately after Task_1, hence 430 result, Task_1 can be scheduled only at time t + e, and will finish at 476 In order to do this, a task must be scheduled by setting: 526 Real-Time Tasks Scheduled by EDF on Multiprocessors. Proceedings of 612 runtime at each instance, and that is scheduled according to the urgency of 735 The above creates 2 threads. The first one, scheduled by SCHED_DEADLINE, 736 executes for 10ms every 100ms. The second one, scheduled at SCHED_FIFO
|
D | sched-domains.rst | 35 through scheduler_tick(). It raises a softirq after the next regularly scheduled
|
D | sched-rt-group.rst | 69 0.00015s. So this group can be scheduled with a period of 0.005s and a run time
|
D | sched-bwc.rst | 137 gave each of these applications half of a cpu-core and they both got scheduled
|
/Documentation/ABI/stable/ |
D | sysfs-class-rfkill | 50 This file was scheduled to be removed in 2014, but due to its
|
/Documentation/driver-api/dmaengine/ |
D | pxa_dma.rst | 122 is raised. Upon this interrupt, a tasklet is scheduled for the physical 133 be raised, and the tasklet will be scheduled once again, having a new
|
/Documentation/core-api/ |
D | workqueue.rst | 153 ``create_*workqueue()`` functions are deprecated and scheduled for 161 resources, scheduled and executed. 372 1. Something being scheduled in rapid succession
|
/Documentation/admin-guide/ |
D | lockup-watchdogs.rst | 51 timestamp every time it is scheduled. If that timestamp is not updated
|
D | cputopology.rst | 142 online: CPUs that are online and being scheduled [cpu_online_mask]
|
/Documentation/usb/ |
D | ehci.rst | 89 limits on the number of periodic transactions that can be scheduled, 225 transfers are fully scheduled, so the main issue is likely to be how
|
/Documentation/driver-api/media/drivers/ |
D | pxa_camera.rst | 170 - Videobuffer3 capture is not scheduled on DMA chain (as it stopped !!!) 186 and Videobuffer3 is scheduled on DMA chain.
|
/Documentation/driver-api/nfc/ |
D | nfc-hci.rst | 241 MSGTXWQ context will then be scheduled and invoke nfc_hci_msg_tx_work(). 246 SMW context gets scheduled and invokes nfc_shdlc_sm_work(). This function
|
/Documentation/networking/ |
D | operstates.rst | 131 scheduled to translate the flag combination to IFLA_OPERSTATE as
|
D | net_dim.rst | 118 will be scheduled and run in a separate thread in order not to add overhead to
|
/Documentation/power/ |
D | runtime_pm.rst | 202 scheduled requests to execute the other callbacks for the same device, 203 except for scheduled autosuspends. 331 not yet expired then an autosuspend is scheduled for the appropriate time 358 hasn't been scheduled (or queued up if 'delay' is 0); if the execution of 359 ->runtime_suspend() is already scheduled and not yet expired, the new
|
/Documentation/networking/device_drivers/ethernet/marvell/ |
D | octeontx2.rst | 37 - Scheduled timers unit (TIM)
|
123