From: Dario Faggioli <raistlin@linux.it>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Wei Liu" <wei.liu2@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <stefano.stabellini@eu.citrix.com>
Subject: Re: [Hackathon minutes] PV frontends/backends and NUMA machines
Date: Tue, 21 May 2013 12:17:39 +0200 [thread overview]
Message-ID: <1369131459.12423.35.camel@Solace> (raw)
In-Reply-To: <CAFLBxZYzYDtzAB4=zUZ3hutnQYA2wAyrkagqCgPZXKSpf9zw4w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2107 bytes --]
On mar, 2013-05-21 at 10:53 +0100, George Dunlap wrote:
> On Tue, May 21, 2013 at 10:24 AM, Wei Liu <wei.liu2@citrix.com> wrote:
> > So the core thing in netback is almost ready, I trust Linux scheduler
> > now and don't pin kthread at all but relevant code shuold be easy to
> > add. I just checked my code, all memory allocation is already node
> > awared.
> >
> > As for the toolstack part, I'm not sure writing the initial node to
> > xenstore will be sufficient. Do we do inter-node migration? If so
> > frontend / backend should also update xenstore information as it
> > migrates?
>
> We can of course migrate the vcpus, but migrating the actual memory
> from one node to another is pretty tricky, particularly for PV guests.
> It won't be something that happens very often; when it does, we will
> need to sort out migrating the backend threads.
>
Indeed.
> > IIRC the memory of a guest is striped through nodes, if it is this case,
> > how can pinning benefit? (I might be talking crap as I don't know much
> > about NUMA and its current status in Xen)
>
> It's striped across nodes *of its NUMA affinity*. So if you have a
> 4-node box, and you set its NUMA affinity to node 3, then the
> allocator will try to get all of the memory from node 3. If its
> affinity is set to {2,3}, then the allocator will stripe it across
> nodes 2 and 3.
>
Right. And other than that, the whole point of work items 1, 2 and 3 (in
George's list, at the beginning of this thread) is to make this striping
even "wiser". So, not only 'memory comes from nodes {2,3}' but '_this_
memory comes from node {2} and _that_ memory comes from {3}'. That's why
we think pinning would do it, but you're right (Wei), that is not true
right now, it will only be when we'll get those work items done. :-)
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-05-21 10:17 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
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 [this message]
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=1369131459.12423.35.camel@Solace \
--to=raistlin@linux.it \
--cc=George.Dunlap@eu.citrix.com \
--cc=roger.pau@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@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.