| /linux/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/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 …]
|
| /linux/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
|
| /linux/Documentation/scheduler/ |
| A D | sched-ext.rst | 5 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 47 sched_ext is used only when the BPF scheduler is loaded and running. 64 BPF scheduler and reverts all tasks back to CFS. 75 ^CEXIT: BPF scheduler unregistered 88 scheduler has been loaded): 198 To match the impedance between the scheduler core and the BPF scheduler, [all …]
|
| A D | sched-design-CFS.rst | 12 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 …]
|
| 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/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/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/drivers/gpu/drm/panthor/ |
| A D | panthor_sched.c | 359 struct drm_gpu_scheduler scheduler; member 835 if (queue->scheduler.ops) in group_free_queue() 836 drm_sched_fini(&queue->scheduler); in group_free_queue() 910 lockdep_assert_held(&ptdev->scheduler->lock); in group_bind_locked() 913 ptdev->scheduler->csg_slots[csg_id].group)) in group_bind_locked() 1705 if (!ptdev->scheduler) in panthor_sched_report_fw_events() 2549 drm_sched_start(&queue->scheduler); in queue_start() 2601 if (ptdev->scheduler) in panthor_sched_report_mmu_fault() 3074 group->ptdev->scheduler->wq, 1, in group_create_queue() 3082 drm_sched = &queue->scheduler; in group_create_queue() [all …]
|
| /linux/tools/sched_ext/ |
| A D | README.md | 51 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/sound/pci/mixart/ |
| A D | mixart_core.h | 218 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/drivers/md/dm-vdo/ |
| A D | action-manager.c | 59 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/drivers/gpu/drm/xe/ |
| A D | Kconfig.profile | 6 be forcefully taken away from scheduler. 12 be forcefully taken away from scheduler. 48 bool "Default configuration of limitation on scheduler timeout" 51 Configures the enablement of limitation on scheduler timeout
|
| /linux/net/mptcp/ |
| A D | ctrl.c | 40 char scheduler[MPTCP_SCHED_NAME_MAX]; member 87 return mptcp_get_pernet(net)->scheduler; in mptcp_get_scheduler() 101 strscpy(pernet->scheduler, "default", sizeof(pernet->scheduler)); in mptcp_pernet_set_defaults() 114 strscpy(pernet->scheduler, name, MPTCP_SCHED_NAME_MAX); in mptcp_set_scheduler() 267 table[6].data = &pernet->scheduler; in mptcp_pernet_new_table()
|
| /linux/drivers/gpu/drm/imagination/ |
| A D | pvr_queue.c | 746 struct pvr_queue, scheduler); in pvr_queue_run_job() 758 drm_sched_stop(&queue->scheduler, bad_job ? &bad_job->base : NULL); in pvr_queue_stop() 770 list_for_each_entry(job, &queue->scheduler.pending_list, base.list) { in pvr_queue_start() 785 drm_sched_start(&queue->scheduler); in pvr_queue_start() 802 struct pvr_queue *queue = container_of(sched, struct pvr_queue, scheduler); in pvr_queue_timedout_job() 907 spin_lock(&queue->scheduler.job_list_lock); in pvr_queue_signal_done_fences() 919 spin_unlock(&queue->scheduler.job_list_lock); in pvr_queue_signal_done_fences() 1251 sched = &queue->scheduler; in pvr_queue_create() 1285 err = drm_sched_init(&queue->scheduler, in pvr_queue_create() 1307 drm_sched_fini(&queue->scheduler); in pvr_queue_create() [all …]
|
| /linux/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/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/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/kernel/ |
| A D | Kconfig.preempt | 80 low level and critical code paths (entry code, scheduler, low 82 execution contexts under scheduler control. 141 This option enables a new scheduler class sched_ext (SCX), which 150 - Rapid scheduler deployments: Non-disruptive swap outs of 160 Documentation/scheduler/sched-ext.rst
|
| /linux/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…
|
| /linux/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
|