From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 4 of 4] Support new xl command cpupool-numa-split
Date: Wed, 08 Dec 2010 14:41:24 +0100 [thread overview]
Message-ID: <4CFF8B04.8080305@ts.fujitsu.com> (raw)
In-Reply-To: <1291815484.13966.4555.camel@zakaz.uk.xensource.com>
On 12/08/10 14:38, Ian Campbell wrote:
> On Wed, 2010-12-08 at 13:17 +0000, Juergen Gross wrote:
>> On 12/08/10 14:12, Ian Campbell wrote:
>>> On Wed, 2010-12-08 at 12:20 +0000, Juergen Gross wrote:
>>>> On 12/08/10 12:16, Ian Campbell wrote:
>>>>> Can this loop be merged with the preceding loop, with the body being the
>>>>> else case of the if?
>>>>
>>>> No. I have to add new cpus first to avoid a cpupool without cpus in between.
>>>
>>> ok.
>>>
>>> I was thinking that because this function only gets here if there is a
>>> single pool that all CPUs must be in that pool -- but that's not
>>> actually true is it? Even if that were the common case there's nothing
>>> to enforce that.
>>
>> Perhaps I should add a comment to avoid a problem later...
>
> That would certainly help.
>
> The alternative would be to bail out if all cpus are not associated with
> Pool-0, not just when there are> 1 pools. That would be consistent with
> the function only acting on the default configuration.
I suspect NUMA systems are subject to cpu hot plug...
I'd prefer the way I've done it before. It isn't too complex and more
flexible.
Juergen
--
Juergen Gross Principal Developer Operating Systems
TSP ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28 Internet: ts.fujitsu.com
D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html
next prev parent reply other threads:[~2010-12-08 13:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 7:10 [PATCH 0 of 4] support of NUMA topology in xl Juergen Gross
2010-11-26 7:10 ` [PATCH 1 of 4] Support getting topology info in libxl Juergen Gross
2010-12-07 17:21 ` Ian Jackson
2010-12-08 10:51 ` Ian Campbell
2010-12-08 12:01 ` Juergen Gross
2010-12-09 12:09 ` Gianni Tedesco
2010-11-26 7:10 ` [PATCH 2 of 4] support topolgy info in xl info Juergen Gross
2010-12-07 17:23 ` Ian Jackson
2010-12-08 5:47 ` Juergen Gross
2010-11-26 7:10 ` [PATCH 3 of 4] Extend cpupools to support numa Juergen Gross
2010-12-07 17:25 ` Ian Jackson
2010-12-08 10:58 ` Ian Campbell
2010-12-08 12:07 ` Juergen Gross
2010-11-26 7:10 ` [PATCH 4 of 4] Support new xl command cpupool-numa-split Juergen Gross
2010-12-07 17:26 ` Ian Jackson
2010-12-07 17:31 ` George Dunlap
2010-12-07 17:34 ` Ian Jackson
2010-12-08 11:16 ` Ian Campbell
2010-12-08 12:20 ` Juergen Gross
2010-12-08 13:12 ` Ian Campbell
2010-12-08 13:17 ` Juergen Gross
2010-12-08 13:38 ` Ian Campbell
2010-12-08 13:41 ` Juergen Gross [this message]
2010-12-08 14:12 ` Ian Campbell
2010-12-09 9:45 ` Juergen Gross
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=4CFF8B04.8080305@ts.fujitsu.com \
--to=juergen.gross@ts.fujitsu.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=xen-devel@lists.xensource.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.