xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Ian Pratt <Ian.Pratt@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [Patch 0/6] Cpupools
Date: Wed, 21 Apr 2010 13:35:37 +0200	[thread overview]
Message-ID: <4BCEE309.6010600@ts.fujitsu.com> (raw)
In-Reply-To: <4FA716B1526C7C4DB0375C6DADBC4EA35562034F38@LONPMAILBOX01.citrite.net>

Ian Pratt wrote:
>> Round 2 for cpupools patches.
>>
>> Changes from 1st version:
>> - create all domains in Pool-0, move to specific pool afterwards
> 
> Do you make sure that the domain is moved to the right pool *before* any memory is assigned to the domain?  It's necessary that the CPU affinity mask gets set appropriately to ensure memory gets allocated from the right node.

Yep. Right after creation the domain is moved to it's target pool, after that
the resources are allocated.


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

  reply	other threads:[~2010-04-21 11:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21 11:15 [Patch 0/6] Cpupools Juergen Gross
2010-04-21 11:22 ` Ian Pratt
2010-04-21 11:35   ` Juergen Gross [this message]
2010-04-21 11:53 ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2010-04-20  9:37 Juergen Gross
2010-04-20 18:48 ` Ian Jackson
2010-04-21  4:44   ` Juergen Gross
2010-04-20 18:49 ` Konrad Rzeszutek Wilk
2010-04-21  4:56   ` 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=4BCEE309.6010600@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --cc=Ian.Pratt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).