xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Tim Deegan <tim@xen.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Matt Wilson <msw@amazon.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Hackathon minutes] PV frontends/backends and NUMA machines
Date: Tue, 21 May 2013 11:28:52 +0100	[thread overview]
Message-ID: <519B4C64.40806@eu.citrix.com> (raw)
In-Reply-To: <20130521102409.GH9626@ocelot.phlegethon.org>

On 05/21/2013 11:24 AM, Tim Deegan wrote:
> At 10:45 +0100 on 21 May (1369133137), George Dunlap wrote:
>> What we would want for a comparable domU -- a domU that was NUMA-aware
>> -- was to have the pfn layout in batches across the nodes to which it
>> will be pinned.  E.g., if a domU has its NUMA affinity set to nodes 2-3,
>> then you'd want the first half of the pfns to come from node 2, the
>> second half from node 3.
>>
>> In both cases, the domain builder will need to call the allocator with
>> specific numa nodes for specific regions of the PFN space.
>
> Ah, so that logic lives in the tools for domU?  I was misremembering.
> Anyway, I think I'm convinced that this is a reasonable thing to do
> the dom0 building code. :)

I don't think it lives anywhere at the moment -- I think at the moment 
the domain builder for both dom0 and domU just call the allocator 
without any directions, and the allocator reads the NUMA affinity mask 
for the domain.  But yes, when we do get guest NUMA support, I think the 
domain builder will be the right place to set up the guest NUMA layout, 
both for domUs and dom0.

Matt Wilson I think has some patches to do the domU layout for HVM 
guests -- if he could post those at some point in the next month, it 
might give a head start to the person implementing this (probably me at 
this point).

  -George

  reply	other threads:[~2013-05-21 10:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 13:44 [Hackathon minutes] PV frontends/backends and NUMA machines Stefano Stabellini
2013-05-20 13:48 ` George Dunlap
2013-05-21  8:32   ` Tim Deegan
2013-05-21  8:47     ` George Dunlap
2013-05-21  8:49       ` George Dunlap
2013-05-21 10:03         ` Dario Faggioli
2013-05-21  9:20       ` Tim Deegan
2013-05-21  9:45         ` George Dunlap
2013-05-21 10:24           ` Tim Deegan
2013-05-21 10:28             ` George Dunlap [this message]
2013-05-21 11:12               ` Dario Faggioli
2013-05-21  9:53         ` Dario Faggioli
2013-05-21 10:06       ` Jan Beulich
2013-05-21 10:30         ` Dario Faggioli
2013-05-21 10:43           ` Jan Beulich
2013-05-21 10:58             ` Dario Faggioli
2013-05-21 11:47               ` Jan Beulich
2013-05-21 13:43                 ` Dario Faggioli
2013-05-24 16:00                   ` George Dunlap
2013-05-25 13:57                     ` Dario Faggioli
2013-05-21  8:44   ` Roger Pau Monné
2013-05-21  9:24     ` Wei Liu
2013-05-21  9:53       ` George Dunlap
2013-05-21 10:17         ` Dario Faggioli
2013-05-21 11:10   ` Dario Faggioli
2013-05-23 17:21     ` Dario Faggioli
2013-05-22  1:28   ` Konrad Rzeszutek Wilk
2013-05-22  7:44     ` Dario Faggioli

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=519B4C64.40806@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=msw@amazon.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --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).