| Subject | Re: [RFC][PATCH 10/22] sched: add a syscall to wait for the next instance | From | Raistlin <> | Date | Thu, 11 Nov 2010 20:33:24 +0100 |
| |
On Thu, 2010-11-11 at 20:21 +0100, Peter Zijlstra wrote: > On Fri, 2010-10-29 at 08:35 +0200, Raistlin wrote: > > > > Introduce sched_wait_interval() syscall (and scheduling class > > interface call). In general, this aims at providing each scheduling > > class with a mean of making one of its own task sleep for some time > > according to some specific rule of the scheduling class itself. > > > Did we have an actual use case for this? I seem to remember that the > last time we seemed to thing job wakeups are due to external events, in > which case we don't need this. > Might find out something, but I mostly agree with what you're saying.
> I think we should try without this patch first and only consider this > once we merged the base functionality and have a solid use-case for > this. > Consider it as already dropped! :-)
Thanks, Dario
-- <<This happens because I choose it to happen!>> (Raistlin Majere) ---------------------------------------------------------------------- Dario Faggioli, ReTiS Lab, Scuola Superiore Sant'Anna, Pisa (Italy)
http://blog.linux.it/raistlin / raistlin@ekiga.net / dario.faggioli@jabber.org [unhandled content-type:application/pgp-signature] |