Home
last modified time | relevance | path

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

123456789

/linux-6.15/net/netfilter/ipvs/
H A Dip_vs_sched.c41 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.15/drivers/gpu/drm/i915/gvt/
H A Dsched_policy.c134 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()
301 &gvt->scheduler; in tbs_sched_clean()
[all …]
H A Dscheduler.c292 struct intel_gvt_workload_scheduler *scheduler = &gvt->scheduler; in shadow_context_status_change() local
851 struct intel_gvt_workload_scheduler *scheduler = &gvt->scheduler; in pick_next_workload() local
860 if (!scheduler->current_vgpu) { in pick_next_workload()
865 if (scheduler->need_reschedule) { in pick_next_workload()
1069 struct intel_gvt_workload_scheduler *scheduler = &gvt->scheduler; in complete_current_workload() local
1144 if (gvt->scheduler.need_reschedule) in complete_current_workload()
1156 struct intel_gvt_workload_scheduler *scheduler = &gvt->scheduler; in workload_thread() local
1233 struct intel_gvt_workload_scheduler *scheduler = &gvt->scheduler; in intel_gvt_wait_vgpu_idle() local
1245 struct intel_gvt_workload_scheduler *scheduler = &gvt->scheduler; in intel_gvt_clean_workload_scheduler() local
1255 kthread_stop(scheduler->thread[i]); in intel_gvt_clean_workload_scheduler()
[all …]
/linux-6.15/Documentation/block/
H A Dswitching-sched.rst5 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 …]
H A Ddeadline-iosched.rst2 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.
H A Dkyber-iosched.rst2 Kyber I/O scheduler tunables
5 The only two tunables for the Kyber scheduler are the target latencies for
/linux-6.15/block/
H A DKconfig.iosched5 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.15/Documentation/scheduler/
H A Dsched-ext.rst5 sched_ext is a scheduler class whose behavior can be defined by a set of BPF
6 programs - the BPF scheduler.
11 * The BPF scheduler can group CPUs however it sees fit and schedule them
14 * The BPF scheduler can be turned on and off dynamically anytime.
23 scheduler binary. The debug dump can also be accessed through the
64 BPF scheduler and reverts all tasks back to CFS.
75 ^CEXIT: BPF scheduler unregistered
88 scheduler has been loaded):
197 To match the impedance between the scheduler core and the BPF scheduler,
300 by a sched_ext scheduler:
[all …]
H A Dsched-design-CFS.rst12 scheduler implemented by Ingo Molnar and merged in Linux 2.6.23. When
14 scheduler's SCHED_OTHER interactivity code. Nowadays, CFS is making room
16 Documentation/scheduler/sched-eevdf.rst.
63 previous vanilla scheduler and RSDL/SD are affected).
83 schedules (or a scheduler tick happens) the task's CPU usage is "accounted
98 way the previous scheduler had, and has no heuristics whatsoever. There is
140 idle timer scheduler in order to avoid to get into priority
155 Classes," an extensible hierarchy of scheduler modules. These modules
159 sched/fair.c implements the CFS scheduler described above.
162 the previous vanilla scheduler did. It uses 100 runqueues (for all 100 RT
[all …]
H A Dsched-nice-design.rst6 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 …]
H A Dsched-energy.rst8 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.15/Documentation/gpu/rfc/
H A Di915_scheduler.rst8 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.15/drivers/gpu/drm/panthor/
H A Dpanthor_sched.c358 struct drm_gpu_scheduler scheduler; member
892 if (queue->scheduler.ops) in group_free_queue()
893 drm_sched_fini(&queue->scheduler); in group_free_queue()
968 lockdep_assert_held(&ptdev->scheduler->lock); in group_bind_locked()
971 ptdev->scheduler->csg_slots[csg_id].group)) in group_bind_locked()
1763 if (!ptdev->scheduler) in panthor_sched_report_fw_events()
2605 drm_sched_start(&queue->scheduler, 0); in queue_start()
2657 if (ptdev->scheduler) in panthor_sched_report_mmu_fault()
3292 .submit_wq = group->ptdev->scheduler->wq, in group_create_queue()
3380 drm_sched = &queue->scheduler; in group_create_queue()
[all …]
/linux-6.15/tools/sched_ext/
H A DREADME.md51 In order to run a sched_ext scheduler, you'll have to run a kernel compiled
93 example, using vmlinux.h allows a scheduler to access fields defined directly
108 bpf_printk("Task %s enabled in example scheduler", p->comm);
119 The scheduler build system will generate this vmlinux.h file as part of the
120 scheduler build pipeline. It looks for a vmlinux file in the following
163 For more scheduler implementations, tools and documentation, visit
168 A simple scheduler that provides an example of a minimal sched_ext scheduler.
184 A "central" scheduler where scheduling decisions are made from a single CPU.
197 A flattened cgroup hierarchy scheduler. This scheduler implements hierarchical
203 Similar to scx_simple, in limited scenarios, this scheduler can perform
[all …]
/linux-6.15/net/mptcp/
H A Dctrl.c41 char scheduler[MPTCP_SCHED_NAME_MAX]; member
94 return mptcp_get_pernet(net)->scheduler; in mptcp_get_scheduler()
109 strscpy(pernet->scheduler, "default", sizeof(pernet->scheduler)); in mptcp_pernet_set_defaults()
114 static int mptcp_set_scheduler(char *scheduler, const char *name) in mptcp_set_scheduler() argument
122 strscpy(scheduler, name, MPTCP_SCHED_NAME_MAX); in mptcp_set_scheduler()
133 char (*scheduler)[MPTCP_SCHED_NAME_MAX] = ctl->data; in proc_scheduler() local
141 strscpy(val, *scheduler, MPTCP_SCHED_NAME_MAX); in proc_scheduler()
145 ret = mptcp_set_scheduler(*scheduler, val); in proc_scheduler()
385 table[6].data = &pernet->scheduler; in mptcp_pernet_new_table()
/linux-6.15/sound/pci/mixart/
H A Dmixart_core.h218 u64 scheduler; member
231 u64 scheduler; member
240 u64 scheduler; member
388 u64 scheduler; member
438 u64 scheduler; member
498 u64 scheduler; member
543 u64 scheduler; member
/linux-6.15/drivers/md/dm-vdo/
H A Daction-manager.c59 vdo_action_scheduler_fn scheduler; member
106 vdo_action_scheduler_fn scheduler, struct vdo *vdo, in vdo_make_action_manager() argument
117 .scheduler = in vdo_make_action_manager()
118 ((scheduler == NULL) ? no_default_action : scheduler), in vdo_make_action_manager()
247 manager->scheduler(manager->context)); in vdo_schedule_default_action()
/linux-6.15/drivers/gpu/drm/xe/
H A DKconfig.profile7 be forcefully taken away from scheduler.
13 be forcefully taken away from scheduler.
49 bool "Default configuration of limitation on scheduler timeout"
52 Configures the enablement of limitation on scheduler timeout
/linux-6.15/kernel/trace/rv/monitors/sched/
H A DKconfig7 Collection of monitors to check the scheduler behaves according to specifications.
8 Enable this to enable all scheduler specification supported by the current kernel.
/linux-6.15/Documentation/tools/rv/
H A Drv-mon-sched.rst24 The scheduler monitor collection is a container for several monitors to model
25 the behaviour of the scheduler. Each monitor describes a specification that
26 the scheduler should follow.
/linux-6.15/drivers/gpu/drm/imagination/
H A Dpvr_queue.c756 struct pvr_queue, scheduler); in pvr_queue_run_job()
768 drm_sched_stop(&queue->scheduler, bad_job ? &bad_job->base : NULL); in pvr_queue_stop()
780 list_for_each_entry(job, &queue->scheduler.pending_list, base.list) { in pvr_queue_start()
795 drm_sched_start(&queue->scheduler, 0); in pvr_queue_start()
812 struct pvr_queue *queue = container_of(sched, struct pvr_queue, scheduler); in pvr_queue_timedout_job()
921 spin_lock(&queue->scheduler.job_list_lock); in pvr_queue_signal_done_fences()
933 spin_unlock(&queue->scheduler.job_list_lock); in pvr_queue_signal_done_fences()
1276 sched = &queue->scheduler; in pvr_queue_create()
1310 err = drm_sched_init(&queue->scheduler, &sched_args); in pvr_queue_create()
1327 drm_sched_fini(&queue->scheduler); in pvr_queue_create()
[all …]
/linux-6.15/tools/testing/kunit/test_data/
H A Dtest_is_test_passed-no_tests_run_no_header.log33 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.15/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/
H A Dtracepoints.rst110 - 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.15/kernel/
H A DKconfig.preempt81 This option provides a scheduler driven preemption model that
99 low level and critical code paths (entry code, scheduler, low
101 execution contexts under scheduler control.
158 This option enables a new scheduler class sched_ext (SCX), which
167 - Rapid scheduler deployments: Non-disruptive swap outs of
177 Documentation/scheduler/sched-ext.rst
/linux-6.15/Documentation/virt/kvm/
H A Dhalt-polling.rst12 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).

123456789