Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932262AbbDIWkt (ORCPT ); Thu, 9 Apr 2015 18:40:49 -0400 Received: from e31.co.us.ibm.com ([32.97.110.149]:48840 "EHLO e31.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755121AbbDIWkq (ORCPT ); Thu, 9 Apr 2015 18:40:46 -0400 Date: Thu, 9 Apr 2015 15:40:40 -0700 From: Nishanth Aravamudan To: Peter Zijlstra Cc: Brice Goglin , Ingo Molnar , linux-kernel@vger.kernel.org, Srikar Dronamraju , Boqun Feng , Anshuman Khandual , linuxppc-dev@lists.ozlabs.org, Benjamin Herrenschmidt , Anton Blanchard Subject: Re: Topology updates and NUMA-level sched domains Message-ID: <20150409224040.GG53918@linux.vnet.ibm.com> References: <20150406214558.GA38501@linux.vnet.ibm.com> <20150407102147.GJ23123@twins.programming.kicks-ass.net> <20150407171410.GA62529@linux.vnet.ibm.com> <20150407194129.GT23123@twins.programming.kicks-ass.net> <552503A1.3050502@inria.fr> <20150408105212.GP21418@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20150408105212.GP21418@twins.programming.kicks-ass.net> X-Operating-System: Linux 3.13.0-40-generic (x86_64) User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 15040922-8236-0000-0000-00000AA8E3D9 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1433 Lines: 36 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/