Searched refs:timeslice (Results 1 – 12 of 12) sorted by relevance
9 support was historically coupled to timeslice length, and timeslice10 units were driven by the HZ tick, so the smallest timeslice was 1/HZ.14 that change), and we also intentionally calibrated the linear timeslice16 understand it, the timeslice graph went like this (cheesy ASCII art21 \ | [timeslice length]
23 specifies when its next timeslice would start execution on the ideal
100 | `-- timeslice110 | | `-- timeslice125 | `-- timeslice180 timeslice The number of milliseconds that a device driver is184 default/* The defaults for spintime and timeslice. When a new187 default timeslice.
154 unsigned long int timeslice; member390 if ((dev->port->waithead == NULL) || (timeslip < dev->timeslice)) in parport_yield()408 if ((dev->port->waithead == NULL) || (timeslip < dev->timeslice)) in parport_yield_blocking()
304 timeslice = self.data[i]305 if timeslice.start > end:308 for cpu in timeslice.rqs:309 self.update_rectangle_cpu(timeslice, cpu)
42 sched_stat contains a timeslice how long a task slept.
253 queues of this cgroup gets a timeslice.258 (i.e., went from 0 to 1 request queued) to get a timeslice for one of262 read when the cgroup is in a waiting (for timeslice) state, the stat264 got a timeslice and will not include the current delta.
130 c) DMA hot chaining timeslice issue
789 tmp->timeslice = parport_default_timeslice; in parport_register_device()930 par_dev->timeslice = parport_default_timeslice; in parport_register_dev_model()
538 t->vars[0].data = &device->timeslice; in parport_device_proc_register()
118 determining the absolute timeslice for a certain process in the CFS scheduler
303 running task's timeslice expires, which is almost always way