[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1337203449.4281.15.camel@twins>
Date: Wed, 16 May 2012 23:24:09 +0200
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: "Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
Cc: David Rientjes <rientjes@...gle.com>,
Nishanth Aravamudan <nacc@...ux.vnet.ibm.com>,
mingo@...nel.org, pjt@...gle.com, paul@...lmenage.org,
akpm@...ux-foundation.org, rjw@...k.pl, nacc@...ibm.com,
paulmck@...ux.vnet.ibm.com, tglx@...utronix.de,
seto.hidetoshi@...fujitsu.com, tj@...nel.org, mschmidt@...hat.com,
berrange@...hat.com, nikunj@...ux.vnet.ibm.com,
vatsa@...ux.vnet.ibm.com, liuj97@...il.com,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: [PATCH v3 5/5] cpusets, suspend: Save and restore cpusets
during suspend/resume
On Wed, 2012-05-16 at 03:46 +0530, Srivatsa S. Bhat wrote:
>
> However, the cpu_active_mask was introduced to handle situations where hotplug
> transition is still in progress, and the scheduler needs to take appropriate
> decisions even with some of its data-structures in an inconsistent/stale state.
> But once the hotplug operation is completed, the scheduler doesn't need to
> depend on cpu_active_mask.
> (And on those lines, making the scheduler work correctly even in such cases
> is only a good-to-have as a robustness measure and not a "bugfix".)
I think those 2(?) cases you found not covered by active mask could
actually happen during a hotplug. So far they simply haven't.
--
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