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....@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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
