On Wed, 2007-03-14 at 10:08 -0700, Jeremy Fitzhardinge wrote: > The actual length of the timeslices is an orthogonal issue. It may be > that you want to give processes more cpu time by making their quanta > longer to compensate for lost cpu time, but that would affect their > real-time characteristics. Or you could keep the quanta small, and give > those processes more of them. > > But all this is getting deep into scheduler design, which is not what I > want to get into; I'm just proposing a better metric for a scheduler to > use in whatever way it wants. >From prior emails I think your suggesting that 1ms (or 5 or 10) of time should actually be a variable X that is changed inside sched_clock(). That's not the purpose of that API call, sched_clock() measure real time period. After reading your emails it sounds like what you really want is similar to accurate state accounting which is used for scheduling purposes. Part of that has already been implemented at least twice that I know of. Accounting real time against specific states was done in two version of microstate accounting. Those are fine starting points for the changes you are wanting. Daniel _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxx https://lists.osdl.org/mailman/listinfo/virtualization
