Re: [patch v5 02/15] sched: set initial load avg of new forked task

Hi Alex, >>> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c >>> index 81fa536..cae5134 100644 >>> --- a/kernel/sched/fair.c >>> +++ b/kernel/sched/fair.c >>> @@ -1509,6 +1509,10 @@ static inline void enqueue_entity_load_avg(struct >>> cfs_rq *cfs_rq, >>> * We track migrations using

Re: [patch v5 02/15] sched: set initial load avg of new forked task

Hi Alex, diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index 81fa536..cae5134 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -1509,6 +1509,10 @@ static inline void enqueue_entity_load_avg(struct cfs_rq *cfs_rq, * We track migrations using entity decay_count =

Re: [patch v5 02/15] sched: set initial load avg of new forked task

On 02/24/2013 06:57 PM, Preeti U Murthy wrote: >> > diff --git a/kernel/sched/core.c b/kernel/sched/core.c >> > index 26058d0..1452e14 100644 >> > --- a/kernel/sched/core.c >> > +++ b/kernel/sched/core.c >> > @@ -1559,6 +1559,7 @@ static void __sched_fork(struct task_struct *p) >> > #if

Re: [patch v5 02/15] sched: set initial load avg of new forked task

On 02/24/2013 06:57 PM, Preeti U Murthy wrote: > Hi Alex, > > On 02/20/2013 11:50 AM, Alex Shi wrote: >> On 02/18/2013 01:07 PM, Alex Shi wrote: >>> New task has no runnable sum at its first runnable time, so its >>> runnable load is zero. That makes burst forking balancing just select >>> few

Re: [patch v5 02/15] sched: set initial load avg of new forked task

Hi Alex, On 02/20/2013 11:50 AM, Alex Shi wrote: > On 02/18/2013 01:07 PM, Alex Shi wrote: >> New task has no runnable sum at its first runnable time, so its >> runnable load is zero. That makes burst forking balancing just select >> few idle cpus to assign tasks if we engage runnable load in

Re: [patch v5 02/15] sched: set initial load avg of new forked task

Hi Alex, On 02/20/2013 11:50 AM, Alex Shi wrote: On 02/18/2013 01:07 PM, Alex Shi wrote: New task has no runnable sum at its first runnable time, so its runnable load is zero. That makes burst forking balancing just select few idle cpus to assign tasks if we engage runnable load in balancing.

Re: [patch v5 02/15] sched: set initial load avg of new forked task

On 02/24/2013 06:57 PM, Preeti U Murthy wrote: Hi Alex, On 02/20/2013 11:50 AM, Alex Shi wrote: On 02/18/2013 01:07 PM, Alex Shi wrote: New task has no runnable sum at its first runnable time, so its runnable load is zero. That makes burst forking balancing just select few idle cpus to

Re: [patch v5 02/15] sched: set initial load avg of new forked task

On 02/24/2013 06:57 PM, Preeti U Murthy wrote: diff --git a/kernel/sched/core.c b/kernel/sched/core.c index 26058d0..1452e14 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -1559,6 +1559,7 @@ static void __sched_fork(struct task_struct *p) #if defined(CONFIG_SMP)

Re: [patch v5 02/15] sched: set initial load avg of new forked task

On 02/18/2013 01:07 PM, Alex Shi wrote: > New task has no runnable sum at its first runnable time, so its > runnable load is zero. That makes burst forking balancing just select > few idle cpus to assign tasks if we engage runnable load in balancing. > > Set initial load avg of new forked task as

Re: [patch v5 02/15] sched: set initial load avg of new forked task

On 02/18/2013 01:07 PM, Alex Shi wrote: New task has no runnable sum at its first runnable time, so its runnable load is zero. That makes burst forking balancing just select few idle cpus to assign tasks if we engage runnable load in balancing. Set initial load avg of new forked task as its

[patch v5 02/15] sched: set initial load avg of new forked task

New task has no runnable sum at its first runnable time, so its runnable load is zero. That makes burst forking balancing just select few idle cpus to assign tasks if we engage runnable load in balancing. Set initial load avg of new forked task as its load weight to resolve this issue.

[patch v5 02/15] sched: set initial load avg of new forked task

New task has no runnable sum at its first runnable time, so its runnable load is zero. That makes burst forking balancing just select few idle cpus to assign tasks if we engage runnable load in balancing. Set initial load avg of new forked task as its load weight to resolve this issue.