[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1470052348.5903.6.camel@gmail.com>
Date: Mon, 01 Aug 2016 13:52:28 +0200
From: Mike Galbraith <umgwanakikbuti@...il.com>
To: Wanpeng Li <kernellwp@...il.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Yuyang Du <yuyang.du@...el.com>,
Ingo Molnar <mingo@...nel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Benjamin Segall <bsegall@...gle.com>,
Paul Turner <pjt@...gle.com>,
Morten Rasmussen <morten.rasmussen@....com>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Matt Fleming <matt@...eblueprint.co.uk>,
Vincent Guittot <vincent.guittot@...aro.org>
Subject: Re: [PATCH 4/4] sched,fair: Fix PELT integrity for new tasks
On Mon, 2016-08-01 at 17:56 +0800, Wanpeng Li wrote:
> 2016-08-01 17:31 GMT+08:00 Mike Galbraith <umgwanakikbuti@...il.com>:
> > On Mon, 2016-08-01 at 15:30 +0800, Wanpeng Li wrote:
> >
> > > What's the meaning of "the task is hashed before we call
> > > wake_up_new_task()"?
> >
> > See fork.c::copy_process()
> >
> > /*
> > * Make it visible to the rest of the system, but dont wake
> > it up yet.
> > * Need tasklist lock for parent etc handling!
> > */
> > write_lock_irq(&tasklist_lock);
> > ....
>
> Thanks Mike, so here "is hashed" means that add to list instead of
> real hashing.
Yeah.
-Mike
Powered by blists - more mailing lists