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
103 | `-- timeslice113 | | `-- timeslice128 | `-- timeslice196 ``timeslice`` The number of milliseconds that a device driver is200 ``default/*`` The defaults for spintime and timeslice. When a new203 default timeslice.
154 unsigned long int timeslice; member391 if ((dev->port->waithead == NULL) || (timeslip < dev->timeslice)) in parport_yield()409 if ((dev->port->waithead == NULL) || (timeslip < dev->timeslice)) in parport_yield_blocking()
308 timeslice = self.data[i]309 if timeslice.start > end:312 for cpu in timeslice.rqs:313 self.update_rectangle_cpu(timeslice, cpu)
42 sched_stat contains a timeslice how long a task slept.
252 queues of this cgroup gets a timeslice.257 (i.e., went from 0 to 1 request queued) to get a timeslice for one of261 read when the cgroup is in a waiting (for timeslice) state, the stat263 got a timeslice and will not include the current delta.
791 tmp->timeslice = parport_default_timeslice; in parport_register_device()933 par_dev->timeslice = parport_default_timeslice; in parport_register_dev_model()
539 t->vars[0].data = &device->timeslice; in parport_device_proc_register()
144 c) DMA hot chaining timeslice issue
118 determining the absolute timeslice for a certain process in the CFS scheduler
273 running task's timeslice expires, which is almost always way
