Messages in this thread | | | From | Paul Turner <> | Date | Tue, 7 May 2013 04:20:55 -0700 | Subject | Re: [PATCH v5 3/7] sched: set initial value of runnable avg for new forked task |
| |
Yes, 1024 was only intended as a starting point. We could also arbitrarily pick something larger, the key is that we pick _something_.
If we wanted to be more exacting about it we could just give them a sched_slice() worth; this would have a few obvious "nice" properties (pun intended).
On Tue, May 7, 2013 at 4:05 AM, Alex Shi <alex.shi@intel.com> wrote: > On 05/07/2013 05:57 PM, Morten Rasmussen wrote: >> Agree. The tracked load of new tasks is often very unstable during first >> couple of ms on loaded systems. I'm not sure if 1024 is the right >> initial value. It may need to be larger. > > Maybe Peter can give a better value according to the experience on > scheduler. :) > > -- > Thanks > Alex
| |