| /linux-6.3-rc2/net/netfilter/ipvs/ |
| A D | ip_vs_sched.c | 41 struct ip_vs_scheduler *scheduler) in ip_vs_bind_scheduler() argument
45 if (scheduler->init_service) { in ip_vs_bind_scheduler()
46 ret = scheduler->init_service(svc); in ip_vs_bind_scheduler()
52 rcu_assign_pointer(svc->scheduler, scheduler); in ip_vs_bind_scheduler()
135 if (scheduler) in ip_vs_scheduler_put()
136 module_put(scheduler->module); in ip_vs_scheduler_put()
171 if (!scheduler) { in register_ip_vs_scheduler()
176 if (!scheduler->name) { in register_ip_vs_scheduler()
191 __func__, scheduler->name); in register_ip_vs_scheduler()
225 if (!scheduler) { in unregister_ip_vs_scheduler()
[all …]
|
| /linux-6.3-rc2/drivers/gpu/drm/i915/gvt/ |
| A D | sched_policy.c | 134 struct intel_gvt_workload_scheduler *scheduler = &gvt->scheduler; in try_to_schedule_next_vgpu() local
143 if (scheduler->next_vgpu == scheduler->current_vgpu) { in try_to_schedule_next_vgpu()
144 scheduler->next_vgpu = NULL; in try_to_schedule_next_vgpu()
166 scheduler->current_vgpu = scheduler->next_vgpu; in try_to_schedule_next_vgpu()
167 scheduler->next_vgpu = NULL; in try_to_schedule_next_vgpu()
214 struct intel_gvt_workload_scheduler *scheduler = &gvt->scheduler; in tbs_sched_func() local
224 scheduler->next_vgpu = vgpu; in tbs_sched_func()
236 if (scheduler->next_vgpu) in tbs_sched_func()
280 &gvt->scheduler; in tbs_sched_init()
302 &gvt->scheduler; in tbs_sched_clean()
[all …]
|
| A D | scheduler.c | 292 struct intel_gvt_workload_scheduler *scheduler = &gvt->scheduler; in shadow_context_status_change() local
850 struct intel_gvt_workload_scheduler *scheduler = &gvt->scheduler; in pick_next_workload() local
859 if (!scheduler->current_vgpu) { in pick_next_workload()
864 if (scheduler->need_reschedule) { in pick_next_workload()
1068 struct intel_gvt_workload_scheduler *scheduler = &gvt->scheduler; in complete_current_workload() local
1143 if (gvt->scheduler.need_reschedule) in complete_current_workload()
1155 struct intel_gvt_workload_scheduler *scheduler = &gvt->scheduler; in workload_thread() local
1232 struct intel_gvt_workload_scheduler *scheduler = &gvt->scheduler; in intel_gvt_wait_vgpu_idle() local
1244 struct intel_gvt_workload_scheduler *scheduler = &gvt->scheduler; in intel_gvt_clean_workload_scheduler() local
1254 kthread_stop(scheduler->thread[i]); in intel_gvt_clean_workload_scheduler()
[all …]
|
| A D | debugfs.c | 98 spin_lock_bh(&gvt->scheduler.mmio_context_lock); in vgpu_mmio_diff_show()
105 spin_unlock_bh(&gvt->scheduler.mmio_context_lock); in vgpu_mmio_diff_show()
|
| /linux-6.3-rc2/Documentation/block/ |
| A D | switching-sched.rst | 5 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
16 It is possible to change the IO scheduler for a given block device on
20 To set a specific scheduler, simply do this::
22 echo SCHEDNAME > /sys/block/DEV/queue/scheduler
24 where SCHEDNAME is the name of a defined IO scheduler, and DEV is the
28 a "cat /sys/block/DEV/queue/scheduler" - the list of valid names
29 will be displayed, with the currently selected scheduler in brackets::
31 # cat /sys/block/sda/queue/scheduler
33 # echo none >/sys/block/sda/queue/scheduler
[all …]
|
| A D | deadline-iosched.rst | 2 Deadline IO scheduler tunables
5 This little file attempts to document how the deadline io scheduler works.
12 selecting an io scheduler on a per-device basis.
19 The goal of the deadline io scheduler is to attempt to guarantee a start
21 tunable. When a read request first enters the io scheduler, it is assigned
49 When we have to move requests from the io scheduler queue to the block
60 Sometimes it happens that a request enters the io scheduler that is contiguous
69 rbtree front sector lookup when the io scheduler merge function is called.
|
| A D | kyber-iosched.rst | 2 Kyber I/O scheduler tunables
5 The only two tunables for the Kyber scheduler are the target latencies for
|
| A D | null_blk.rst | 111 Enable/disable the io scheduler.
114 0 nullb* use default blk-mq io scheduler
115 1 nullb* doesn't use io scheduler
|
| /linux-6.3-rc2/block/ |
| A D | Kconfig.iosched | 5 tristate "MQ deadline I/O scheduler"
8 MQ version of the deadline IO scheduler.
11 tristate "Kyber I/O scheduler"
14 The Kyber I/O scheduler is a low-overhead scheduler suitable for
20 tristate "BFQ I/O scheduler"
23 BFQ I/O scheduler for BLK-MQ. BFQ distributes the bandwidth of
|
| /linux-6.3-rc2/Documentation/gpu/rfc/ |
| A D | i915_scheduler.rst | 8 i915 with the DRM scheduler is:
32 * Convert the i915 to use the DRM scheduler
33 * GuC submission backend fully integrated with DRM scheduler
35 handled in DRM scheduler)
36 * Resets / cancels hook in DRM scheduler
37 * Watchdog hooks into DRM scheduler
39 integrated with DRM scheduler (e.g. state machine gets
47 * ROI low on fully integrating into DRM scheduler
49 scheduler
53 * Will be an optional feature in the DRM scheduler
[all …]
|
| /linux-6.3-rc2/Documentation/scheduler/ |
| A D | sched-design-CFS.rst | 10 scheduler implemented by Ingo Molnar and merged in Linux 2.6.23. It is the
11 replacement for the previous vanilla scheduler's SCHED_OTHER interactivity
59 previous vanilla scheduler and RSDL/SD are affected).
79 schedules (or a scheduler tick happens) the task's CPU usage is "accounted
94 way the previous scheduler had, and has no heuristics whatsoever. There is
133 idle timer scheduler in order to avoid to get into priority
148 Classes," an extensible hierarchy of scheduler modules. These modules
149 encapsulate scheduling policy details and are handled by the scheduler core
152 sched/fair.c implements the CFS scheduler described above.
155 the previous vanilla scheduler did. It uses 100 runqueues (for all 100 RT
[all …]
|
| A D | sched-nice-design.rst | 6 nice-levels implementation in the new Linux scheduler.
12 scheduler, (otherwise we'd have done it long ago) because nice level
16 In the O(1) scheduler (in 2003) we changed negative nice levels to be
77 With the old scheduler, if you for example started a niced task with +1
88 The new scheduler in v2.6.23 addresses all three types of complaints:
91 enough), the scheduler was decoupled from 'time slice' and HZ concepts
94 support: with the new scheduler nice +19 tasks get a HZ-independent
96 scheduler.
99 the new scheduler makes nice(1) have the same CPU utilization effect on
101 scheduler, running a nice +10 and a nice 11 task has the same CPU
[all …]
|
| A D | sched-energy.rst | 8 Energy Aware Scheduling (or EAS) gives the scheduler the ability to predict
23 The actual EM used by EAS is _not_ maintained by the scheduler, but by a
50 scheduler. This alternative considers two objectives: energy-efficiency and
53 The idea behind introducing an EM is to allow the scheduler to evaluate the
56 time, the EM must be as simple as possible to minimize the scheduler latency
60 for the scheduler to decide where a task should run (during wake-up), the EM
71 EAS (as well as the rest of the scheduler) uses the notion of 'capacity' to
87 The scheduler manages references to the EM objects in the topology code when the
115 Please note that the scheduler will create two duplicate list nodes for
121 manipulated by the scheduler.
[all …]
|
| /linux-6.3-rc2/sound/pci/mixart/ |
| A D | mixart_core.h | 218 u64 scheduler; member
231 u64 scheduler; member
240 u64 scheduler; member
388 u64 scheduler; member
439 u64 scheduler; member
499 u64 scheduler; member
544 u64 scheduler; member
|
| /linux-6.3-rc2/tools/testing/kunit/test_data/ |
| A D | test_is_test_passed-no_tests_run_no_header.log | 33 io scheduler noop registered
34 io scheduler deadline registered
35 io scheduler cfq registered (default)
36 io scheduler mq-deadline registered
37 io scheduler kyber registered
|
| /linux-6.3-rc2/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| A D | tracepoints.rst | 110 - mlx5_esw_vport_qos_create: trace creation of transmit scheduler arbiter for vport::
117 - mlx5_esw_vport_qos_config: trace configuration of transmit scheduler arbiter for vport::
124 - mlx5_esw_vport_qos_destroy: trace deletion of transmit scheduler arbiter for vport::
131 - mlx5_esw_group_qos_create: trace creation of transmit scheduler arbiter for rate group::
138 - mlx5_esw_group_qos_config: trace configuration of transmit scheduler arbiter for rate group::
145 - mlx5_esw_group_qos_destroy: trace deletion of transmit scheduler arbiter for group::
|
| /linux-6.3-rc2/Documentation/virt/kvm/ |
| A D | halt-polling.rst | 12 before giving up the cpu to the scheduler in order to let something else run.
15 very quickly by at least saving us a trip through the scheduler, normally on
18 interval or some other task on the runqueue is runnable the scheduler is
21 savings of not invoking the scheduler are distinguishable.
34 The maximum time for which to poll before invoking the scheduler, referred to
77 whether the scheduler is invoked within that function).
|
| /linux-6.3-rc2/drivers/gpu/drm/i915/ |
| A D | i915_getparam.c | 67 value = !!(i915->caps.scheduler & I915_SCHEDULER_CAP_SEMAPHORES); in i915_getparam_ioctl()
113 value = i915->caps.scheduler; in i915_getparam_ioctl()
|
| /linux-6.3-rc2/Documentation/translations/zh_CN/scheduler/ |
| A D | schedutil.rst | 4 :Original: Documentation/scheduler/schedutil.rst
89 …- Documentation/translations/zh_CN/scheduler/sched-capacity.rst:"1. CPU Capacity + 2. Task utiliza…
|
| A D | sched-bwc.rst | 3 :Original: Documentation/scheduler/sched-bwc.rst
19 SCHED_RT的情况在Documentation/scheduler/sched-rt-group.rst中有涉及。
|
| /linux-6.3-rc2/Documentation/admin-guide/mm/ |
| A D | multigen_lru.rst | 100 When a new job comes in, the job scheduler needs to find out whether
103 scheduler needs to estimate the working sets of the existing jobs.
133 A typical use case is that a job scheduler runs this command at a
142 comes in, the job scheduler wants to proactively reclaim cold pages on
157 A typical use case is that a job scheduler runs this command before it
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/usb/ |
| A D | da8xx-usb.txt | 35 - reg-names: "controller", "scheduler", "queuemgr"
75 reg-names = "controller", "scheduler", "queuemgr";
|
| /linux-6.3-rc2/drivers/gpu/drm/i915/gt/ |
| A D | intel_engine_user.c | 131 i915->caps.scheduler = enabled & ~disabled; in set_scheduler_caps()
132 if (!(i915->caps.scheduler & I915_SCHEDULER_CAP_ENABLED)) in set_scheduler_caps()
133 i915->caps.scheduler = 0; in set_scheduler_caps()
|
| /linux-6.3-rc2/net/sched/ |
| A D | Kconfig | 16 If you say N here, you will get the standard packet scheduler, which
75 scheduler.
83 Say Y here if you want to use an n-band queue packet scheduler
208 tristate "Deficit Round Robin scheduler (DRR)"
219 tristate "Multi-queue priority scheduler (MQPRIO)"
232 tristate "SKB priority queue scheduler (SKBPRIO)"
235 scheduler. This schedules packets according to skb->priority,
245 tristate "CHOose and Keep responsive flow scheduler (CHOKE)"
256 tristate "Quick Fair Queueing scheduler (QFQ)"
326 Enhanced scheduler packet scheduling algorithm.
[all …]
|
| /linux-6.3-rc2/Documentation/admin-guide/cgroup-v1/ |
| A D | cpusets.rst | 60 CPUs or Memory Nodes not in that cpuset. The scheduler will not
106 kernel to avoid any additional impact on the critical scheduler or
294 the system load imposed by a batch scheduler monitoring this
299 counter, a batch scheduler can detect memory pressure with a
304 the batch scheduler can obtain the key information, memory
400 linearly with the number of CPUs being balanced. So the scheduler
512 The internal kernel cpuset to scheduler interface passes from the
513 cpuset code to the scheduler code a partition of the load balanced
549 then scheduler migrate task B to CPU Y so that task B can start on
557 idle CPUs, the scheduler might not search all CPUs in the domain
[all …]
|