All of lore.kernel.org
 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>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Hackathon minutes] PV frontends/backends and NUMA machines
Date: Tue, 21 May 2013 09:47:09 +0100	[thread overview]
Message-ID: <CAFLBxZbSj0E7r9pmFpcpTFtBQOQsDK4NcftUEULqemBksEab3g@mail.gmail.com> (raw)
In-Reply-To: <20130521083251.GD9626@ocelot.phlegethon.org>

On Tue, May 21, 2013 at 9:32 AM, Tim Deegan <tim@xen.org> wrote:
> At 14:48 +0100 on 20 May (1369061330), George Dunlap wrote:
>> So the work items I remember are as follows:
>> 1. Implement NUMA affinity for vcpus
>> 2. Implement Guest NUMA support for PV guests
>> 3. Teach Xen how to make a sensible NUMA allocation layout for dom0
>
> Does Xen need to do this?  Or could dom0 sort that out for itself after
> boot?

There are two aspects of this.  First would be, if dom0.nvcpus <
host.npcpus, to place the vcpus reasonably on the various numa nodes.

The second is to make the pfn -> NUMA node layout reasonable.  At the
moment, as I understand it, pfns will be striped across nodes.  In
theory dom0 could deal with this, but it seems like in practice it's
going to be nasty trying to sort that stuff out.  It would be much
better, if you have (say) 4 nodes and 4GiB of memory assigned to dom0,
to have pfn 0-1G on node 0, 1-2G on node 2, &c.

 -George

  reply	other threads:[~2013-05-21  8:47 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 [this message]
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
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=CAFLBxZbSj0E7r9pmFpcpTFtBQOQsDK4NcftUEULqemBksEab3g@mail.gmail.com \
    --to=george.dunlap@eu.citrix.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 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.