Messages in this thread | | | Date | Mon, 17 Jun 2013 08:33:28 +0800 | From | Alex Shi <> | Subject | Re: [patch v8 3/9] sched: set initial value of runnable avg for new forked task |
| |
On 06/15/2013 08:09 PM, Lei Wen wrote: >>>>> >>> > and make forking balancing imbalance since incorrect load_avg_contrib. >>>>> >>> > >>>>> >>> > Further more, Morten Rasmussen notice some tasks were not launched at >>>>> >>> > once after created. So Paul and Peter suggest giving a start value for >>>>> >>> > new task runnable avg time same as sched_slice(). >>> >> I am confused at this comment, how set slice to runnable avg would change >>> >> the behavior of "some tasks were not launched at once after created"? >> > >> > I also don't know the details on Morten's machine. but just guess, there >> > are much tasks on in the run queue. the minimum load avg make the new >> > task wait its time... > Is there some possibility that since task structure is allocated without being > set to 0, and it cause the imbalance between runqueues. Then the new forked > is migrated to other cpus, so that it cause its execution being delayed?
Is there sth weird happens? The task should be running a while before migration. and periodic load balance also need some time to happen. So generally, it has no such worries.
-- Thanks Alex
| |