Home
last modified time | relevance | path

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

123456

/linux/net/netfilter/ipvs/
H A Dip_vs_sched.c40 struct ip_vs_scheduler *scheduler) in ip_vs_bind_scheduler() argument
44 if (scheduler->init_service) { in ip_vs_bind_scheduler()
45 ret = scheduler->init_service(svc); in ip_vs_bind_scheduler()
51 rcu_assign_pointer(svc->scheduler, scheduler); in ip_vs_bind_scheduler()
63 sched = rcu_dereference_protected(svc->scheduler, 1); in ip_vs_unbind_scheduler()
68 rcu_assign_pointer(svc->scheduler, NULL); in ip_vs_unbind_scheduler()
132 void ip_vs_scheduler_put(struct ip_vs_scheduler *scheduler) in ip_vs_scheduler_put() argument
134 if (scheduler) in ip_vs_scheduler_put()
135 module_put(scheduler->module); in ip_vs_scheduler_put()
144 struct ip_vs_scheduler *sched = rcu_dereference(svc->scheduler); in ip_vs_scheduler_err()
[all …]
/linux/drivers/gpu/drm/i915/gvt/
H A Dsched_policy.c135 struct intel_gvt_workload_scheduler *scheduler = &gvt->scheduler; in try_to_schedule_next_vgpu() local
144 if (scheduler->next_vgpu == scheduler->current_vgpu) { in try_to_schedule_next_vgpu()
145 scheduler->next_vgpu = NULL; in try_to_schedule_next_vgpu()
153 scheduler->need_reschedule = true; in try_to_schedule_next_vgpu()
157 if (scheduler->current_workload[engine->id]) in try_to_schedule_next_vgpu()
162 vgpu_update_timeslice(scheduler->current_vgpu, cur_time); in try_to_schedule_next_vgpu()
163 vgpu_data = scheduler->next_vgpu->sched_data; in try_to_schedule_next_vgpu()
167 scheduler->current_vgpu = scheduler->next_vgpu; in try_to_schedule_next_vgpu()
168 scheduler->next_vgpu = NULL; in try_to_schedule_next_vgpu()
170 scheduler->need_reschedule = false; in try_to_schedule_next_vgpu()
[all …]
/linux/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/Documentation/scheduler/
H A Dsched-ext.rst7 sched_ext is a scheduler class whose behavior can be defined by a set of BPF
8 programs - the BPF scheduler.
13 * The BPF scheduler can group CPUs however it sees fit and schedule them
16 * The BPF scheduler can be turned on and off dynamically anytime.
18 * The system integrity is maintained no matter what the BPF scheduler does.
23 * When the BPF scheduler triggers an error, debug information is dumped to
25 scheduler binary. The debug dump can also be accessed through the
27 triggers a debug dump. This doesn't terminate the BPF scheduler and can
47 sched_ext is used only when the BPF scheduler is loaded and running.
50 treated as ``SCHED_NORMAL`` and scheduled by the fair-class scheduler until the
[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
89 scheduler maintains a singly linked list of all performance domains intersecting
115 Please note that the scheduler will create two duplicate list nodes for
[all …]
/linux/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/kernel/trace/rv/monitors/sts/
H A DKconfig11 Monitor to ensure relationships between scheduler and task switches
12 * the scheduler is called and returns with interrupts disabled
13 * each call to the scheduler has up to one switch
14 * switches only happen inside the scheduler
15 * each call to the scheduler disables interrupts to switch
/linux/Documentation/gpu/rfc/
H A Di915_scheduler.rst8 i915 with the DRM scheduler is:
14 * Lots of rework will need to be done to integrate with DRM scheduler so
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
41 * Execlists backend will minimum required to hook in the DRM scheduler
44 be difficult to integrate with the DRM scheduler and these
[all …]
/linux/drivers/gpu/drm/panthor/
H A Dpanthor_sched.c352 struct drm_gpu_scheduler scheduler; member
735 if (!queue_work((group)->ptdev->scheduler->wq, &(group)->wname ## _work)) \
924 if (queue->scheduler.ops) in group_free_queue()
925 drm_sched_fini(&queue->scheduler); in group_free_queue()
1005 lockdep_assert_held(&ptdev->scheduler->lock); in group_bind_locked()
1008 ptdev->scheduler->csg_slots[csg_id].group)) in group_bind_locked()
1015 csg_slot = &ptdev->scheduler->csg_slots[csg_id]; in group_bind_locked()
1046 lockdep_assert_held(&ptdev->scheduler->lock); in group_unbind_locked()
1054 slot = &ptdev->scheduler->csg_slots[group->csg_id]; in group_unbind_locked()
1102 mod_delayed_work(queue->scheduler.timeout_wq, in queue_reset_timeout_locked()
[all …]
/linux/tools/sched_ext/
H A DREADME.md51 In order to run a sched_ext scheduler, you'll have to run a kernel compiled
86 example, using vmlinux.h allows a scheduler to access fields defined directly
101 bpf_printk("Task %s enabled in example scheduler", p->comm);
112 The scheduler build system will generate this vmlinux.h file as part of the
113 scheduler build pipeline. It looks for a vmlinux file in the following
156 For more scheduler implementations, tools and documentation, visit
161 A simple scheduler that provides an example of a minimal sched_ext scheduler.
164 Though very simple, in limited scenarios, this scheduler can perform reasonably
169 Another simple, yet slightly more complex scheduler tha
[all...]
/linux/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/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/kernel/trace/rv/monitors/sched/
H A DKconfig8 Collection of monitors to check the scheduler behaves according to specifications.
9 Enable this to enable all scheduler specification supported by the current kernel.
/linux/drivers/gpu/drm/imagination/
H A Dpvr_queue.c663 struct pvr_queue *queue = container_of(job->base.sched, struct pvr_queue, scheduler); in pvr_queue_submit_job_to_cccb()
808 struct pvr_queue, scheduler); in pvr_queue_run_job()
822 drm_sched_stop(&queue->scheduler, bad_job ? &bad_job->base : NULL); in pvr_queue_stop()
834 list_for_each_entry(job, &queue->scheduler.pending_list, base.list) { in pvr_queue_start()
849 drm_sched_start(&queue->scheduler, 0); in pvr_queue_start()
868 struct pvr_queue *queue = container_of(sched, struct pvr_queue, scheduler); in pvr_queue_timedout_job()
977 spin_lock(&queue->scheduler.job_list_lock); in pvr_queue_signal_done_fences()
979 list_for_each_entry_safe(job, tmp_job, &queue->scheduler.pending_list, base.list) { in pvr_queue_signal_done_fences()
989 spin_unlock(&queue->scheduler.job_list_lock); in pvr_queue_signal_done_fences()
1223 struct pvr_queue *queue = container_of(job->base.sched, struct pvr_queue, scheduler); in pvr_queue_job_push()
[all …]
/linux/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/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/kernel/
H A DKconfig.preempt84 This option provides a scheduler driven preemption model that
102 low level and critical code paths (entry code, scheduler, low
104 execution contexts under scheduler control.
179 This option enables a new scheduler class sched_ext (SCX), which
188 - Rapid scheduler deployments: Non-disruptive swap outs of
198 Documentation/scheduler/sched-ext.rst
/linux/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).
/linux/Documentation/translations/zh_CN/scheduler/
H A Dschedutil.rst4 :Original: Documentation/scheduler/schedutil.rst
89 …- Documentation/translations/zh_CN/scheduler/sched-capacity.rst:"1. CPU Capacity + 2. Task utiliza…
/linux/Documentation/admin-guide/mm/
H A Dmultigen_lru.rst100 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
158 A typical use case is that a job scheduler runs this command before it
/linux/Documentation/devicetree/bindings/usb/
H A Dda8xx-usb.txt35 - reg-names: "controller", "scheduler", "queuemgr"
75 reg-names = "controller", "scheduler", "queuemgr";
/linux/net/sched/
H A DKconfig16 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)"
222 Say Y here if you want to use the Multi-queue Priority scheduler.
223 This scheduler allows QOS to be offloaded on NICs that have support
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)"
[all …]

123456