From: Peter Zijlstra <peterz@infradead.org>
To: Brice Goglin <Brice.Goglin@inria.fr>
Cc: Boqun Feng <boqun.feng@linux.vnet.ibm.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Nishanth Aravamudan <nacc@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Anton Blanchard <anton@samba.org>,
linuxppc-dev@lists.ozlabs.org,
Anshuman Khandual <khandual@linux.vnet.ibm.com>
Subject: Re: Topology updates and NUMA-level sched domains
Date: Wed, 8 Apr 2015 12:52:12 +0200 [thread overview]
Message-ID: <20150408105212.GP21418@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <552503A1.3050502@inria.fr>
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.
> 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.
> Is there a convenient way to be notified when a CPU (or memory)
> is unplugged?
I think you can poll some sysfs file or other.
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Brice Goglin <Brice.Goglin@inria.fr>
Cc: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Boqun Feng <boqun.feng@linux.vnet.ibm.com>,
Anshuman Khandual <khandual@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Anton Blanchard <anton@samba.org>
Subject: Re: Topology updates and NUMA-level sched domains
Date: Wed, 8 Apr 2015 12:52:12 +0200 [thread overview]
Message-ID: <20150408105212.GP21418@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <552503A1.3050502@inria.fr>
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.
> 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.
> Is there a convenient way to be notified when a CPU (or memory)
> is unplugged?
I think you can poll some sysfs file or other.
next prev parent reply other threads:[~2015-04-08 10:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 21:45 Topology updates and NUMA-level sched domains Nishanth Aravamudan
2015-04-06 21:45 ` Nishanth Aravamudan
2015-04-07 10:21 ` Peter Zijlstra
2015-04-07 10:21 ` Peter Zijlstra
2015-04-07 17:14 ` Nishanth Aravamudan
2015-04-07 17:14 ` Nishanth Aravamudan
2015-04-07 19:41 ` Peter Zijlstra
2015-04-07 19:41 ` Peter Zijlstra
2015-04-08 10:32 ` Brice Goglin
2015-04-08 10:32 ` Brice Goglin
2015-04-08 10:52 ` Peter Zijlstra [this message]
2015-04-08 10:52 ` Peter Zijlstra
2015-04-09 22:40 ` Nishanth Aravamudan
2015-04-09 22:40 ` Nishanth Aravamudan
2015-04-09 22:37 ` Nishanth Aravamudan
2015-04-09 22:37 ` Nishanth Aravamudan
2015-04-09 22:29 ` Nishanth Aravamudan
2015-04-09 22:29 ` Nishanth Aravamudan
2015-04-10 8:31 ` Peter Zijlstra
2015-04-10 8:31 ` Peter Zijlstra
2015-04-10 9:08 ` Peter Zijlstra
2015-04-10 9:08 ` Peter Zijlstra
2015-04-10 19:50 ` Nishanth Aravamudan
2015-04-10 19:50 ` Nishanth Aravamudan
2015-04-10 20:30 ` Nishanth Aravamudan
2015-04-10 20:30 ` Nishanth Aravamudan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150408105212.GP21418@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Brice.Goglin@inria.fr \
--cc=anton@samba.org \
--cc=boqun.feng@linux.vnet.ibm.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=nacc@linux.vnet.ibm.com \
--cc=srikar@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.