[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150409224040.GG53918@linux.vnet.ibm.com>
Date: Thu, 9 Apr 2015 15:40:40 -0700
From: Nishanth Aravamudan <nacc@...ux.vnet.ibm.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Brice Goglin <Brice.Goglin@...ia.fr>,
Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
Boqun Feng <boqun.feng@...ux.vnet.ibm.com>,
Anshuman Khandual <khandual@...ux.vnet.ibm.com>,
linuxppc-dev@...ts.ozlabs.org,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Anton Blanchard <anton@...ba.org>
Subject: Re: Topology updates and NUMA-level sched domains
On 08.04.2015 [12:52:12 +0200], Peter Zijlstra wrote:
> On Wed, Apr 08, 2015 at 12:32:01PM +0200, Brice Goglin wrote:
> > Le 07/04/2015 21:41, Peter Zijlstra a écrit :
> > > No, that's very much not the same. Even if it were dealing with hotplug
> > > it would still assume the cpu to return to the same node.
> > >
> > > But mostly people do not even bother to handle hotplug.
> > >
> >
> > You said userspace assumes the cpu<->node relation is a boot-time fixed
> > one, and hotplug breaks this.
>
> I said no such thing. Regular hotplug actually respects that relation.
Wel, sort of. If you *just* hotplug a CPU out, your invariant of what
CPUs are currently available on what nodes is no longer held. Similarly
if you just add a CPU. And means that you could end up using cpumasks
that are incorrect if you don't make them at runtime, it seems?
> > How do you expect userspace to handle hotplug?
>
> Mostly not. Why would they? CPU hotplug is rare and mostly a case of:
> don't do that then.
>
> Its just that some of the virt wankers are using it for resource
> management which is entirely misguided. Then again, most of virt is.
I guess that is a matter of opinion.
-Nish
--
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