Home
last modified time | relevance | path

Searched refs:scheduler (Results 1 – 103 of 103) sorted by relevance

/linux-4.4.14/net/netfilter/ipvs/
Dip_vs_sched.c46 struct ip_vs_scheduler *scheduler) in ip_vs_bind_scheduler() argument
50 if (scheduler->init_service) { in ip_vs_bind_scheduler()
51 ret = scheduler->init_service(svc); in ip_vs_bind_scheduler()
57 rcu_assign_pointer(svc->scheduler, scheduler); in ip_vs_bind_scheduler()
70 cur_sched = rcu_dereference_protected(svc->scheduler, 1); in ip_vs_unbind_scheduler()
138 void ip_vs_scheduler_put(struct ip_vs_scheduler *scheduler) in ip_vs_scheduler_put() argument
140 if (scheduler) in ip_vs_scheduler_put()
141 module_put(scheduler->module); in ip_vs_scheduler_put()
150 struct ip_vs_scheduler *sched = rcu_dereference(svc->scheduler); in ip_vs_scheduler_err()
172 int register_ip_vs_scheduler(struct ip_vs_scheduler *scheduler) in register_ip_vs_scheduler() argument
[all …]
DKconfig111 comment "IPVS scheduler"
254 comment 'IPVS SH scheduler'
261 The source hashing scheduler maps source IPs to destinations
Dip_vs_ctl.c846 sched = rcu_dereference_protected(svc->scheduler, 1); in __ip_vs_update_dest()
850 sched = rcu_dereference_protected(svc->scheduler, 1); in __ip_vs_update_dest()
1082 sched = rcu_dereference_protected(svc->scheduler, 1); in __ip_vs_unlink_dest()
1332 old_sched = rcu_dereference_protected(svc->scheduler, 1); in ip_vs_edit_service()
1336 RCU_INIT_POINTER(svc->scheduler, NULL); in ip_vs_edit_service()
1388 old_sched = rcu_dereference_protected(svc->scheduler, 1); in __ip_vs_del_service()
2005 struct ip_vs_scheduler *sched = rcu_dereference(svc->scheduler); in ip_vs_info_seq_show()
2464 sched = rcu_dereference_protected(src->scheduler, 1); in ip_vs_copy_service()
2952 sched = rcu_dereference_protected(svc->scheduler, 1); in ip_vs_genl_fill_service()
Dip_vs_core.c331 sched = rcu_dereference(svc->scheduler); in ip_vs_sched_persist()
504 sched = rcu_dereference(svc->scheduler); in ip_vs_schedule()
/linux-4.4.14/Documentation/block/
Dswitching-sched.txt5 Each io queue has a set of io scheduler tunables associated with it. These
6 tunables control how the io scheduler works. You can find these entries
17 IO scheduler for a given block device on the fly (thus making it possible,
18 for instance, to set the CFQ scheduler for the system default, but
22 To set a specific scheduler, simply do this:
24 echo SCHEDNAME > /sys/block/DEV/queue/scheduler
26 where SCHEDNAME is the name of a defined IO scheduler, and DEV is the
30 a "cat /sys/block/DEV/queue/scheduler" - the list of valid names
31 will be displayed, with the currently selected scheduler in brackets:
33 # cat /sys/block/hda/queue/scheduler
[all …]
Ddeadline-iosched.txt1 Deadline IO scheduler tunables
4 This little file attempts to document how the deadline io scheduler works.
11 selecting an io scheduler on a per-device basis.
20 The goal of the deadline io scheduler is to attempt to guarantee a start
22 tunable. When a read request first enters the io scheduler, it is assigned
50 When we have to move requests from the io scheduler queue to the block
61 Sometimes it happens that a request enters the io scheduler that is contiguous
70 rbtree front sector lookup when the io scheduler merge function is called.
D00-INDEX8 - CFQ IO scheduler tunables
14 - Deadline IO scheduler tunables
16 - Block io priorities (in CFQ scheduler)
Dqueue-sysfs.txt135 scheduler (RW)
138 for this block device. The currently active IO scheduler will be enclosed
139 in [] brackets. Writing an IO scheduler name to this file will switch
140 control of this block device to that new IO scheduler. Note that writing
141 an IO scheduler name to this file will attempt to load that IO scheduler
Drequest.txt23 I I/O scheduler member
38 void *elevator_private I I/O scheduler private data
Dbiodoc.txt49 - I/O scheduler modularization
70 4. The I/O scheduler
116 Various parameters that the generic i/o scheduler logic uses are set at
224 iii. The i/o scheduler algorithm itself can be replaced/set as appropriate
226 As in 2.4, it is possible to plugin a brand new i/o scheduler for a particular
229 of the i/o scheduler. There are more pluggable callbacks, e.g for init,
233 the i/o scheduler from block drivers.
235 I/O scheduler wrappers are to be used instead of accessing the queue directly.
236 See section 4. The I/O scheduler for details.
374 on to the generic block layer, only to be merged by the i/o scheduler
[all …]
Dcfq-iosched.txt4 The main aim of CFQ scheduler is to provide a fair allocation of the disk
45 This parameter allows the scheduler to anticipate requests in the "backward"
55 So scheduler will not bias toward one or the other request (otherwise scheduler
87 scheduler. If latency mode (called low_latency) is enabled, CFQ tries
223 CFQ IO scheduler Idling Theory
/linux-4.4.14/block/
DKconfig.iosched9 The no-op I/O scheduler is a minimal scheduler that does basic merging
16 tristate "Deadline I/O scheduler"
19 The deadline I/O scheduler is simple and compact. It will provide
25 tristate "CFQ I/O scheduler"
28 The CFQ I/O scheduler tries to distribute bandwidth equally
33 This is the default I/O scheduler.
43 prompt "Default I/O scheduler"
46 Select the I/O scheduler which will be used by default for all
/linux-4.4.14/Documentation/scheduler/
Dsched-design-CFS.txt9 scheduler implemented by Ingo Molnar and merged in Linux 2.6.23. It is the
10 replacement for the previous vanilla scheduler's SCHED_OTHER interactivity
56 previous vanilla scheduler and RSDL/SD are affected).
76 schedules (or a scheduler tick happens) the task's CPU usage is "accounted
89 other HZ detail. Thus the CFS scheduler has no notion of "timeslices" in the
90 way the previous scheduler had, and has no heuristics whatsoever. There is
95 which can be used to tune the scheduler from "desktop" (i.e., low latencies) to
97 for desktop workloads. SCHED_BATCH is handled by the CFS scheduler module too.
99 Due to its design, the CFS scheduler is not prone to any of the "attacks" that
100 exist today against the heuristics of the stock scheduler: fiftyp.c, thud.c,
[all …]
Dsched-nice-design.txt2 nice-levels implementation in the new Linux scheduler.
8 scheduler, (otherwise we'd have done it long ago) because nice level
12 In the O(1) scheduler (in 2003) we changed negative nice levels to be
73 With the old scheduler, if you for example started a niced task with +1
84 The new scheduler in v2.6.23 addresses all three types of complaints:
87 enough), the scheduler was decoupled from 'time slice' and HZ concepts
90 support: with the new scheduler nice +19 tasks get a HZ-independent
92 scheduler.
95 the new scheduler makes nice(1) have the same CPU utilization effect on
97 scheduler, running a nice +10 and a nice 11 task has the same CPU
[all …]
D00-INDEX12 - How and why the scheduler's nice levels are implemented.
Dsched-arch.txt13 To request the scheduler call switch_to with the runqueue unlocked,
18 penalty to the core scheduler implementation in the CONFIG_SMP case.
Dsched-deadline.txt51 every time the task wakes up, the scheduler computes a "scheduling deadline"
77 the scheduler checks if
155 to the number of CPUs), then the scheduler is unable to respect all the
169 More precisely, it can be proven that using a global EDF scheduler the
354 Documentation/scheduler/sched-rt-group.txt), and is based on readable/
480 available as a GitHub repository: https://github.com/scheduler-tools.
487 workloads (maybe mimicking real use-cases) and evaluate how the scheduler
489 rt-app is available at: https://github.com/scheduler-tools/rt-app.
513 https://github.com/scheduler-tools/schedtool-dl.git.
Dsched-stats.txt42 scheduler. We kept it for ABI compatibility, but it is always set to zero.
152 under the scheduler's policies. A simple version of such a program is
Dsched-bwc.txt5 The SCHED_RT case is covered in Documentation/scheduler/sched-rt-group.txt ]
Dsched-rt-group.txt77 lack an EDF scheduler to make non-uniform periods usable.
/linux-4.4.14/sound/pci/mixart/
Dmixart_core.h230 u64 scheduler; member
243 u64 scheduler; member
252 u64 scheduler; member
393 u64 scheduler; member
444 u64 scheduler; member
504 u64 scheduler; member
549 u64 scheduler; member
/linux-4.4.14/drivers/gpu/drm/amd/amdgpu/
DMakefile8 -Idrivers/gpu/drm/amd/scheduler
89 ../scheduler/gpu_scheduler.o \
90 ../scheduler/sched_fence.o \
/linux-4.4.14/net/sched/
DKconfig15 If you say N here, you will get the standard packet scheduler, which
57 CBQ is a commonly used scheduler, so if you're unsure, you should
91 Say Y here if you want to use the ATM pseudo-scheduler. This
105 scheduler.
113 Say Y here if you want to use an n-band queue packet scheduler
210 tristate "Deficit Round Robin scheduler (DRR)"
221 tristate "Multi-queue priority scheduler (MQPRIO)"
223 Say Y here if you want to use the Multi-queue Priority scheduler.
224 This scheduler allows QOS to be offloaded on NICs that have support
233 tristate "CHOose and Keep responsive flow scheduler (CHOKE)"
[all …]
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-cfq-target-latency6 when the user sets cfq to /sys/block/<device>/scheduler.
Dsysfs-kernel-uids14 Documentation/scheduler/sched-design-CFS.txt
Dsysfs-class-led26 scheduler is chosen. Trigger specific parameters can appear in
/linux-4.4.14/Documentation/cgroups/
Dcpusets.txt57 CPUs or Memory Nodes not in that cpuset. The scheduler will not
103 kernel to avoid any additional impact on the critical scheduler or
278 the system load imposed by a batch scheduler monitoring this
283 counter, a batch scheduler can detect memory pressure with a
288 the batch scheduler can obtain the key information, memory
376 The kernel scheduler (kernel/sched/core.c) automatically load balances
384 linearly with the number of CPUs being balanced. So the scheduler
416 scheduler will avoid load balancing across the CPUs in that cpuset,
421 enabled, then the scheduler will have one sched domain covering all
434 scheduler might not consider the possibility of load balancing that
[all …]
Dblkio-controller.txt226 scheduler queues for service. This can be greater than the total time
261 waiting in the scheduler queue. This is in nanoseconds. If this is
277 This is the amount of time spent by the IO scheduler idling for a
/linux-4.4.14/Documentation/timers/
D00-INDEX14 - Summary of the different methods for the scheduler clock-interrupts management.
Dtimers-howto.txt41 help the scheduler, power management, and just make your
84 With the introduction of a range, the scheduler is
Dtimekeeping.txt118 determining the absolute timeslice for a certain process in the CFS scheduler
123 much more often, especially by the scheduler. If you have to do trade-offs
DNO_HZ.txt176 6. The LB_BIAS scheduler feature is disabled by adaptive ticks.
228 scheduler will decide where to run them, which might or might not be
Dhighres.txt238 systems, where the time slice is controlled by the scheduler, variable
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dpicoxcell.txt17 Note: two timers are required - one for the scheduler clock and one for the
Didle-states.txt95 An operating system scheduler may need to compute the shortest wake-up delay
101 In other words, the scheduler can make its scheduling decision by selecting
/linux-4.4.14/arch/mn10300/kernel/
Dmn10300-serial-low.S62 # - induces a scheduler tick timer interrupt when done, which we then subvert
109 # - induces a scheduler tick timer interrupt when done, which we then subvert
/linux-4.4.14/tools/perf/Documentation/
Dperf-timechart.txt18 of an arbitrary workload. By default timechart records only scheduler
24 on the events in the perf.data file, timechart will contain scheduler/cpu
Dperf-sched.txt6 perf-sched - Tool to trace/measure scheduler properties (latencies)
Dperf-bench.txt67 Suite for evaluating performance of scheduler and IPC mechanisms.
/linux-4.4.14/arch/sparc/
DKconfig318 bool "SMT (Hyperthreading) scheduler support"
322 SMT scheduler support improves the CPU scheduler's decision making
327 bool "Multi-core scheduler support"
331 Multi-core scheduler support improves the CPU scheduler's decision
/linux-4.4.14/Documentation/powerpc/
Ddscr.txt29 default DSCR value, scheduler will write the changed value which will
34 gets used directly in the scheduler process context switch at all.
/linux-4.4.14/arch/sh/mm/
DKconfig230 bool "Multi-core scheduler support"
234 Multi-core scheduler support improves the CPU scheduler's decision
/linux-4.4.14/Documentation/vm/
Dnuma99 later migrate away from that memory. The Linux scheduler is aware of the
101 structures [see Documentation/scheduler/sched-domains.txt]--and the scheduler
103 the scheduler does not take a task's NUMA footprint into account directly.
Dpage_migration27 Manual migration is useful if for example the scheduler has relocated
28 a process to a processor on a distant node. A batch scheduler or an
Dactive_mm.txt28 and that the scheduler might as well try to avoid wasting time on
Duserfaultfd.txt96 page faults in the guest scheduler so those guest processes that
/linux-4.4.14/Documentation/devicetree/bindings/usb/
Dam33xx-usb.txt59 - reg-names: glue, controller, scheduler, queuemgr
190 reg-names = "glue", "controller", "scheduler", "queuemgr";
/linux-4.4.14/arch/x86/crypto/
Dsha512-ssse3-asm.S129 add WK_2(idx), T1 # W[t] + K[t] from message scheduler
160 # scheduler.
170 # by one tab. Vectored instructions (for the message scheduler) are indented
311 # +1 iteration because the scheduler leads hashing by 1 iteration
Dsha512-avx-asm.S136 add WK_2(idx), T1 # W[t] + K[t] from message scheduler
166 # scheduler.
312 # +1 iteration because the scheduler leads hashing by 1 iteration
/linux-4.4.14/include/net/
Dip_vs.h638 struct ip_vs_scheduler __rcu *scheduler; /* bound scheduler object */ member
1353 int register_ip_vs_scheduler(struct ip_vs_scheduler *scheduler);
1354 int unregister_ip_vs_scheduler(struct ip_vs_scheduler *scheduler);
1356 struct ip_vs_scheduler *scheduler);
1360 void ip_vs_scheduler_put(struct ip_vs_scheduler *scheduler);
/linux-4.4.14/drivers/usb/host/
Du132-hcd.c172 struct delayed_work scheduler; member
180 struct delayed_work scheduler; member
313 if (queue_delayed_work(workqueue, &ring->scheduler, delta)) in u132_ring_requeue_work()
315 } else if (queue_delayed_work(workqueue, &ring->scheduler, 0)) in u132_ring_requeue_work()
329 if (cancel_delayed_work(&ring->scheduler)) in u132_ring_cancel_work()
392 if (queue_delayed_work(workqueue, &endp->scheduler, delta)) in u132_endp_queue_work()
398 if (cancel_delayed_work(&endp->scheduler)) in u132_endp_cancel_work()
1304 container_of(work, struct u132_ring, scheduler.work); in u132_hcd_ring_work_scheduler()
1367 container_of(work, struct u132_endp, scheduler.work); in u132_hcd_endp_work_scheduler()
1883 INIT_DELAYED_WORK(&endp->scheduler, u132_hcd_endp_work_scheduler); in create_endpoint_and_queue_int()
[all …]
/linux-4.4.14/Documentation/
Dkernel-per-CPU-kthreads.txt107 1. Avoid sending scheduler IPIs to the CPU to be de-jittered,
110 CPU awakens, the scheduler will send an IPI that can result in
116 scheduler-clock interrupts that the de-jittered CPU receives,
122 This further reduces the number of scheduler-clock interrupts
Dlockup-watchdogs.txt71 the scheduler, which would prevent the "nohz_full" functionality
Dworkqueue.txt121 management by hooking into the scheduler. The worker-pool is notified
185 managed by the system scheduler.
216 execution is regulated by the system scheduler.
Dthis_cpu_ops.txt215 so is expensive. If there are other reasons why the scheduler cannot
222 and the scheduler cannot preempt, then they are safe. If any interrupts
D00-INDEX400 scheduler/
401 - directory with info on the scheduler.
Dstatic-keys.txt250 Since there are a number of static key API uses in the scheduler paths,
Drbtree.txt30 packets in the "hierarchical token bucket" scheduler.
Dkernel-parameters.txt71 IOSCHED More than one I/O scheduler is enabled.
1646 isolcpus= [KNL,SMP] Isolate CPUs from the general scheduler.
2397 noautogroup Disable scheduler automatic task group creation.
2519 steal time is computed, but won't influence scheduler
3344 [KNL, SMP] Set scheduler's default relax_domain_level.
3447 sched_debug [KNL] Enables verbose scheduler debug messages.
3742 The scheduler will make use of this information and
Dmemory-barriers.txt1893 try to enter the scheduler, where it will eventually encounter
/linux-4.4.14/Documentation/thermal/
Dintel_powerclamp.txt95 are not masked. Tests show that the extra wakeups from scheduler tick
209 non-intrusive to the scheduler or the IRQ core code.
282 appear running to the scheduler. But the overall system idle is still
/linux-4.4.14/tools/power/cpupower/po/
Dde.po690 " -m, --sched-mc [VAL] Sets the kernel's multi core scheduler policy.\n"
696 " -s, --sched-smt [VAL] Sets the kernel's thread sibling scheduler "
744 msgid " -m, --sched-mc Gets the kernel's multi core scheduler policy.\n"
750 " -s, --sched-smt Gets the kernel's thread sibling scheduler policy.\n"
762 msgid "System's multi core scheduler setting: "
773 msgid "System's thread sibling scheduler setting: "
Dit.po687 " -m, --sched-mc [VAL] Sets the kernel's multi core scheduler policy.\n"
693 " -s, --sched-smt [VAL] Sets the kernel's thread sibling scheduler "
741 msgid " -m, --sched-mc Gets the kernel's multi core scheduler policy.\n"
748 " -s, --sched-smt Gets the kernel's thread sibling scheduler policy.\n"
760 msgid "System's multi core scheduler setting: "
771 msgid "System's thread sibling scheduler setting: "
Dcs.po679 " -m, --sched-mc [VAL] Sets the kernel's multi core scheduler policy.\n"
685 " -s, --sched-smt [VAL] Sets the kernel's thread sibling scheduler "
733 msgid " -m, --sched-mc Gets the kernel's multi core scheduler policy.\n"
739 " -s, --sched-smt Gets the kernel's thread sibling scheduler policy.\n"
751 msgid "System's multi core scheduler setting: "
762 msgid "System's thread sibling scheduler setting: "
Dfr.po679 " -m, --sched-mc [VAL] Sets the kernel's multi core scheduler policy.\n"
685 " -s, --sched-smt [VAL] Sets the kernel's thread sibling scheduler "
733 msgid " -m, --sched-mc Gets the kernel's multi core scheduler policy.\n"
739 " -s, --sched-smt Gets the kernel's thread sibling scheduler policy.\n"
751 msgid "System's multi core scheduler setting: "
762 msgid "System's thread sibling scheduler setting: "
Dpt.po689 " -m, --sched-mc [VAL] Sets the kernel's multi core scheduler policy.\n"
695 " -s, --sched-smt [VAL] Sets the kernel's thread sibling scheduler "
743 msgid " -m, --sched-mc Gets the kernel's multi core scheduler policy.\n"
750 " -s, --sched-smt Gets the kernel's thread sibling scheduler policy.\n"
762 msgid "System's multi core scheduler setting: "
773 msgid "System's thread sibling scheduler setting: "
/linux-4.4.14/net/bluetooth/
DKconfig25 HCI device and connection manager, scheduler
/linux-4.4.14/arch/arm64/
DKconfig480 bool "Multi-core scheduler support"
482 Multi-core scheduler support improves the CPU scheduler's decision
487 bool "SMT scheduler support"
489 Improves the CPU scheduler's decision making when dealing with
/linux-4.4.14/Documentation/leds/
Dleds-class.txt27 You can change triggers in a similar manner to the way an IO scheduler
/linux-4.4.14/tools/power/cpupower/bench/
DREADME-BENCH114 -p, --prio=<priority> scheduler priority, HIGH, LOW or DEFAULT
/linux-4.4.14/arch/arc/kernel/
Dentry.S44 ; put last task in scheduler queue
/linux-4.4.14/Documentation/networking/
Deql.txt240 The slave scheduler probably could be replaced with a dozen other
251 One version of the scheduler was able to push 5.3 K/s through the
Dtimestamping.txt83 Request tx timestamps prior to entering the packet scheduler. Kernel
132 scheduler. In that case timestamps will be queued onto the error
240 possible to construct a packet scheduler configuration that delays
Doperstates.txt87 set this flag. On netif_carrier_off(), the scheduler stops sending
Dscaling.txt253 When the scheduler moves a thread to a new CPU while it has outstanding
261 in both tables is identical. This is likely false if the scheduler has
/linux-4.4.14/init/
DKconfig879 # For architectures that want to enable the support for NUMA-affine scheduler
908 bool "Memory placement aware NUMA scheduler"
935 - Documentation/scheduler/sched-design-CFS.txt (CFS)
1082 bool "Group CPU scheduler"
1085 This feature lets CPU scheduler recognize task groups and control CPU
1101 tasks running within the fair group scheduler. Groups with no limit
1104 See tip/Documentation/scheduler/sched-bwc.txt for more information.
1115 See Documentation/scheduler/sched-rt-group.txt for more information.
1128 Currently, CFQ IO scheduler uses it to recognize task groups and
1234 This option optimizes the scheduler for common desktop workloads by
/linux-4.4.14/arch/s390/
DKconfig474 prompt "Topology scheduler support"
480 Topology scheduler support improves the CPU scheduler's decision
/linux-4.4.14/arch/ia64/
DKconfig355 bool "SMT scheduler support"
358 Improves the CPU scheduler's decision making when dealing with
/linux-4.4.14/lib/
DKconfig.debug846 bool "Collect scheduler debugging info"
851 that can help debug the scheduler. The runtime overhead of this
859 bool "Collect scheduler statistics"
864 scheduler and related routines to collect statistics about
865 scheduler behavior and provide them in /proc/schedstat. These
866 stats may be useful for both tuning and debugging the scheduler
867 If you aren't debugging the scheduler or trying to tune a specific
/linux-4.4.14/arch/arm/boot/dts/
Ddm816x.dtsi474 reg-names = "glue", "controller", "scheduler", "queuemgr";
Dam33xx.dtsi619 reg-names = "glue", "controller", "scheduler", "queuemgr";
/linux-4.4.14/Documentation/device-mapper/
Dcache-policies.txt22 trying to see when the io scheduler has let the ios run.
/linux-4.4.14/arch/powerpc/
DKconfig628 bool "SMT (Hyperthreading) scheduler support"
631 SMT scheduler support improves the CPU scheduler's decision making
/linux-4.4.14/Documentation/isdn/
DREADME.hysdn170 0x00001000 Log the asynchronous scheduler actions (config and log)
/linux-4.4.14/arch/arm/
DKconfig1364 bool "Multi-core scheduler support"
1367 Multi-core scheduler support improves the CPU scheduler's decision
1372 bool "SMT scheduler support"
1375 Improves the CPU scheduler's decision making when dealing with
/linux-4.4.14/Documentation/ia64/
Dmca.txt112 The scheduler hooks used by ia64 (curr_task, set_curr_task) are layer
/linux-4.4.14/Documentation/frv/
Dfeatures.txt52 The kernel scheduler runs at 100Hz irrespective of the clock speed on this
/linux-4.4.14/arch/x86/
DKconfig876 bool "SMT (Hyperthreading) scheduler support"
879 SMT scheduler support improves the CPU scheduler's decision making
886 prompt "Multi-core scheduler support"
889 Multi-core scheduler support improves the CPU scheduler's decision
2460 processor goes idle (as is done by the scheduler). The
/linux-4.4.14/Documentation/development-process/
D3.Early-stage23 access to the realtime scheduler. This module was implemented and sent to
/linux-4.4.14/arch/arm/mach-imx/
DKconfig594 prompt "Clocksource for scheduler clock"
/linux-4.4.14/Documentation/RCU/
Dstallwarn.txt238 o A hardware or software issue shuts off the scheduler-clock
DwhatisRCU.txt348 c. RCU applied to scheduler and interrupt/NMI-handler tasks.
/linux-4.4.14/arch/
DKconfig61 scheduler functionality, networking code and KVM have such
/linux-4.4.14/arch/mips/
DKconfig2176 bool "SMT (multithreading) scheduler support"
2180 SMT scheduler support improves the CPU scheduler's decision making
/linux-4.4.14/Documentation/security/
Dcredentials.txt489 the scheduler and others of the changes.
/linux-4.4.14/Documentation/scsi/
DChangeLog.ncr53c8xx466 This has been called 'silly scheduler'.
DChangeLog.lpfc985 * Removed usused scheduler prototypes in lpfc_crtn.h
/linux-4.4.14/arch/s390/kernel/
Dentry.S694 brasl %r14,schedule # call scheduler
/linux-4.4.14/Documentation/virtual/kvm/
Dtimekeeping.txt579 paravirtualized scheduler clock, which reveals the true amount of CPU time for
/linux-4.4.14/Documentation/trace/
Dftrace.txt1448 and not the average. We can have a very fast scheduler that may
1498 end of the scheduler.
/linux-4.4.14/
DCREDITS2409 D: tc: HFSC scheduler
3057 D: nl.linux.org administrator, minor scheduler additions
/linux-4.4.14/Documentation/filesystems/
Dproc.txt1124 psched Global packet scheduler parameters.
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt2499 session.html> , with breakpoints being set in the scheduler and in an