Home
last modified time | relevance | path

Searched refs:timeslice (Results 1 – 18 of 18) sorted by relevance

/Linux-v6.1/Documentation/scheduler/
Dsched-nice-design.rst13 support was historically coupled to timeslice length, and timeslice
14 units were driven by the HZ tick, so the smallest timeslice was 1/HZ.
18 that change), and we also intentionally calibrated the linear timeslice
20 understand it, the timeslice graph went like this (cheesy ASCII art
25 \ | [timeslice length]
Dsched-design-CFS.rst24 specifies when its next timeslice would start execution on the ideal
/Linux-v6.1/drivers/gpu/drm/i915/selftests/
Dintel_scheduler_helpers.c38 saved->timeslice = engine->props.timeslice_duration_ms; in intel_selftest_modify_policy()
82 engine->props.timeslice_duration_ms = saved->timeslice; in intel_selftest_restore_policy()
Dintel_scheduler_helpers.h18 u64 timeslice; member
/Linux-v6.1/Documentation/admin-guide/
Dparport.rst103 | `-- timeslice
113 | | `-- timeslice
128 | `-- timeslice
196 ``timeslice`` The number of milliseconds that a device driver is
200 ``default/*`` The defaults for spintime and timeslice. When a new
203 default timeslice.
/Linux-v6.1/include/linux/
Dparport.h154 unsigned long int timeslice; member
424 if ((dev->port->waithead == NULL) || (timeslip < dev->timeslice)) in parport_yield()
442 if ((dev->port->waithead == NULL) || (timeslip < dev->timeslice)) in parport_yield_blocking()
/Linux-v6.1/tools/perf/scripts/python/
Dsched-migration.py306 timeslice = self.data[i]
307 if timeslice.start > end:
310 for cpu in timeslice.rqs:
311 self.update_rectangle_cpu(timeslice, cpu)
/Linux-v6.1/Documentation/translations/zh_CN/scheduler/
Dsched-nice-design.rst30 \ | [timeslice length]
/Linux-v6.1/Documentation/admin-guide/cgroup-v1/
Dblkio-controller.rst207 queues of this cgroup gets a timeslice.
212 (i.e., went from 0 to 1 request queued) to get a timeslice for one of
216 read when the cgroup is in a waiting (for timeslice) state, the stat
218 got a timeslice and will not include the current delta.
/Linux-v6.1/tools/perf/Documentation/
Dperf-inject.txt53 sched_stat contains a timeslice how long a task slept.
/Linux-v6.1/drivers/gpu/drm/i915/
DKconfig.profile115 is scheduled for execution for the timeslice duration, before
/Linux-v6.1/drivers/parport/
Dprocfs.c540 t->vars[0].data = &device->timeslice; in parport_device_proc_register()
Dshare.c802 par_dev->timeslice = parport_default_timeslice; in parport_register_dev_model()
/Linux-v6.1/Documentation/driver-api/media/drivers/
Dpxa_camera.rst146 c) DMA hot chaining timeslice issue
/Linux-v6.1/drivers/gpu/drm/i915/gt/
Dselftest_execlists.c1134 unsigned long timeslice; in live_timeslice_rewind() local
1153 timeslice = xchg(&engine->props.timeslice_duration_ms, 1); in live_timeslice_rewind()
1246 engine->props.timeslice_duration_ms = timeslice; in live_timeslice_rewind()
1278 timeout = 2 * msecs_to_jiffies_timeout(timeslice(engine)); in slice_timeout()
1433 unsigned long timeslice; in live_timeslice_nopreempt() local
1445 timeslice = xchg(&engine->props.timeslice_duration_ms, 1); in live_timeslice_nopreempt()
1512 xchg(&engine->props.timeslice_duration_ms, timeslice); in live_timeslice_nopreempt()
Dintel_execlists_submission.c1202 static unsigned long timeslice(const struct intel_engine_cs *engine) in timeslice() function
1227 duration = timeslice(engine); in start_timeslice()
/Linux-v6.1/Documentation/timers/
Dtimekeeping.rst119 determining the absolute timeslice for a certain process in the CFS scheduler
Dno_hz.rst275 running task's timeslice expires, which is almost always way