Home
last modified time | relevance | path

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

/kernel/linux/linux-5.10/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
/kernel/linux/linux-5.10/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.
/kernel/linux/linux-5.10/include/linux/
Dparport.h154 unsigned long int timeslice; member
383 if ((dev->port->waithead == NULL) || (timeslip < dev->timeslice)) in parport_yield()
401 if ((dev->port->waithead == NULL) || (timeslip < dev->timeslice)) in parport_yield_blocking()
/kernel/linux/linux-5.10/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)
/kernel/linux/linux-5.10/Documentation/admin-guide/cgroup-v1/
Dblkio-controller.rst202 queues of this cgroup gets a timeslice.
207 (i.e., went from 0 to 1 request queued) to get a timeslice for one of
211 read when the cgroup is in a waiting (for timeslice) state, the stat
213 got a timeslice and will not include the current delta.
/kernel/linux/linux-5.10/tools/perf/Documentation/
Dperf-inject.txt46 sched_stat contains a timeslice how long a task slept.
/kernel/linux/linux-5.10/drivers/gpu/drm/i915/
DKconfig.profile101 is scheduled for execution for the timeslice duration, before
/kernel/linux/linux-5.10/Documentation/driver-api/media/drivers/
Dpxa_camera.rst146 c) DMA hot chaining timeslice issue
/kernel/linux/linux-5.10/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()
/kernel/linux/linux-5.10/drivers/gpu/drm/i915/gt/
Dselftest_lrc.c1136 unsigned long timeslice; in live_timeslice_rewind() local
1155 timeslice = xchg(&engine->props.timeslice_duration_ms, 1); in live_timeslice_rewind()
1248 engine->props.timeslice_duration_ms = timeslice; in live_timeslice_rewind()
1280 timeout = 2 * msecs_to_jiffies_timeout(timeslice(engine)); in slice_timeout()
1437 unsigned long timeslice; in live_timeslice_nopreempt() local
1449 timeslice = xchg(&engine->props.timeslice_duration_ms, 1); in live_timeslice_nopreempt()
1516 xchg(&engine->props.timeslice_duration_ms, timeslice); in live_timeslice_nopreempt()
Dintel_lrc.c1977 timeslice(const struct intel_engine_cs *engine) in timeslice() function
1993 return timeslice(engine); in active_timeslice()
2024 duration = timeslice(engine); in start_timeslice()
/kernel/linux/linux-5.10/Documentation/timers/
Dtimekeeping.rst119 determining the absolute timeslice for a certain process in the CFS scheduler
Dno_hz.rst279 running task's timeslice expires, which is almost always way