[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGjg+kEKE3T0h8Z1YHourT3iVW_nb8FkAUZ9jnOE8Urxo2KpxQ@mail.gmail.com>
Date: Sun, 23 Dec 2012 20:00:33 +0800
From: Alex Shi <lkml.alex@...il.com>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Alex Shi <alex.shi@...el.com>, rob@...dley.net, mingo@...hat.com,
peterz@...radead.org, gregkh@...uxfoundation.org,
andre.przywara@....com, rjw@...k.pl, paul.gortmaker@...driver.com,
akpm@...ux-foundation.org, paulmck@...ux.vnet.ibm.com,
linux-kernel@...r.kernel.org, pjt@...gle.com,
vincent.guittot@...aro.org
Subject: Re: [PATCH 06/18] sched: set initial load avg of new forked task as
its load weight
>> update_curr(cfs_rq);
>> account_entity_enqueue(cfs_rq, se);
>> - enqueue_entity_load_avg(cfs_rq, se, flags & ENQUEUE_WAKEUP);
>> + enqueue_entity_load_avg(cfs_rq, se, flags &
>> + (ENQUEUE_WAKEUP | ENQUEUE_NEWTASK));
>
> It seems that just passing 'flags' is enough.
Uh, Yes, it's true. will remove this.
>
>>
>> if (flags & ENQUEUE_WAKEUP) {
>> place_entity(cfs_rq, se, 0);
>> @@ -2586,6 +2594,7 @@ enqueue_task_fair(struct rq *rq, struct task_struct *p, int flags)
>> cfs_rq->h_nr_running++;
>>
>> flags = ENQUEUE_WAKEUP;
>> + flags &= ~ENQUEUE_NEWTASK;
>
> Why is this needed?
Uh. not needed, will remove this too. Thanks a lot!
--
Thanks
Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists