|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] Xen 3.4.1 NUMA support
To: |
Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>, Andre Przywara <andre.przywara@xxxxxxx>, George Dunlap <George.Dunlap@xxxxxxxxxxxxx> |
Subject: |
RE: [Xen-devel] Xen 3.4.1 NUMA support |
From: |
Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx> |
Date: |
Fri, 13 Nov 2009 15:40:51 +0000 |
Accept-language: |
en-US |
Acceptlanguage: |
en-US |
Cc: |
Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, Papagiannis, Anastasios <apapag@xxxxxxxxxxxx> |
Delivery-date: |
Fri, 13 Nov 2009 07:41:44 -0800 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<C7232B60.1A0BA%keir.fraser@xxxxxxxxxxxxx> |
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
List-post: |
<mailto:xen-devel@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<4FA716B1526C7C4DB0375C6DADBC4EA342A71C17C9@xxxxxxxxxxxxxxxxxxxxxxxxx> <C7232B60.1A0BA%keir.fraser@xxxxxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Thread-index: |
Acpka+pZmF499CPITS21072Y6vG4PAAAFTTAAAJj9MAAAGcVwA== |
Thread-topic: |
[Xen-devel] Xen 3.4.1 NUMA support |
> > I'd really like to see us enumerate pCPUs in a sensible order so that
> it's
> > easier to see the topology. It should be nodes.sockets.cores{.threads},
> > leaving gaps for missing execution units due to hot plug or non power of
> two
> > packing.
> > Right now we're inconsistent in the enumeration order depending on how
> the
> > BIOS has set things up. It would be great if someone could volunteer to
> fix
> > this...
>
> Even better would be to have pCPUs addressable and listable explicitly as
> dotted tuples. That can be implemented entirely within the toolstack, and
> could even allow wildcarding of tuple components to efficiently express
> cpumasks.
Yes, I'd certainly like to see the toolstack support dotted tuple notation.
However, I just don't trust the toolstack to get this right unless xen has
already set it up nicely for it with a sensible enumeration and defined
sockets-per-node, cores-per-socket and threads-per-core parameters. Xen should
provide a clean interface to the toolstack in this respect.
Ian
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-devel] Xen 3.4.1 NUMA support, (continued)
- Re: [Xen-devel] Xen 3.4.1 NUMA support, Andre Przywara
- RE: [Xen-devel] Xen 3.4.1 NUMA support, Ian Pratt
- Re: [Xen-devel] Xen 3.4.1 NUMA support, Keir Fraser
- RE: [Xen-devel] Xen 3.4.1 NUMA support,
Ian Pratt <=
- Re: [Xen-devel] Xen 3.4.1 NUMA support, Keir Fraser
- Re: [Xen-devel] Xen 3.4.1 NUMA support, George Dunlap
- RE: [Xen-devel] Xen 3.4.1 NUMA support, Ian Pratt
- Re: [Xen-devel] Xen 3.4.1 NUMA support, Keir Fraser
- RE: [Xen-devel] Xen 3.4.1 NUMA support, Ian Pratt
- Re: [Xen-devel] Xen 3.4.1 NUMA support, Jan Beulich
- RE: [Xen-devel] Xen 3.4.1 NUMA support, Ian Pratt
- RE: [Xen-devel] Xen 3.4.1 NUMA support, Jan Beulich
- Re: [Xen-devel] Xen 3.4.1 NUMA support, Keir Fraser
- Re: [Xen-devel] Xen 3.4.1 NUMA support, Keir Fraser
|
|
|
|
|