From: Dario Faggioli <raistlin@linux.it>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andre Przywara <andre.przywara@amd.com>,
Anil Madhavapeddy <anil@recoil.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel <xen-devel@lists.xen.org>,
George Dunlap <dunlapg@gmail.com>,
Yang Z Zhang <yang.z.zhang@intel.com>
Subject: Re: NUMA TODO-list for xen-devel
Date: Thu, 02 Aug 2012 15:21:36 +0200 [thread overview]
Message-ID: <1343913696.4873.7.camel@Solace> (raw)
In-Reply-To: <501A672B02000078000921EA@nat28.tlf.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 1093 bytes --]
On Thu, 2012-08-02 at 10:40 +0100, Jan Beulich wrote:
> >>> On 01.08.12 at 18:30, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
> > - Xen NUMA internals. Placing items such as the per-cpu stacks and data
> > area on the local NUMA node, rather than unconditionally on node 0 at
> > the moment. As part of this, there will be changes to
> > alloc_{dom,xen}heap_page() to allow specification of which node(s) to
> > allocate memory from.
>
> Those interfaces already support flags to be passed, including a
> node ID. It just needs to be made use of in more places.
>
Yes, I also remember it being already node_affinity conscious, and think
it's more a matter of how it is called. I'll update the wiki accordingly
(it doesn't need to contain these sort of details anyway).
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/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:[~2012-08-02 13:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 16:16 NUMA TODO-list for xen-devel Dario Faggioli
2012-08-01 16:24 ` Dario Faggioli
2012-08-01 16:30 ` Andrew Cooper
2012-08-01 16:47 ` Dario Faggioli
2012-08-01 16:53 ` Andrew Cooper
2012-08-02 9:40 ` Jan Beulich
2012-08-02 13:21 ` Dario Faggioli [this message]
2012-08-01 16:32 ` Anil Madhavapeddy
2012-08-01 16:58 ` Dario Faggioli
2012-08-02 0:04 ` Malte Schwarzkopf
2012-08-07 23:53 ` Dario Faggioli
2012-08-02 1:04 ` Zhang, Yang Z
2012-08-07 22:56 ` Dario Faggioli
2012-08-02 9:43 ` Jan Beulich
2012-08-02 13:34 ` Dario Faggioli
2012-08-02 14:07 ` Jan Beulich
2012-08-02 16:36 ` George Dunlap
2012-08-03 9:23 ` Jan Beulich
2012-08-03 9:48 ` Andre Przywara
2012-08-03 10:03 ` Jan Beulich
2012-08-03 22:40 ` Dan Magenheimer
2012-08-03 11:00 ` George Dunlap
2012-08-03 22:34 ` Dan Magenheimer
2012-08-06 7:15 ` Jan Beulich
2012-08-06 16:28 ` Dan Magenheimer
2012-08-03 10:02 ` Andre Przywara
2012-08-03 10:40 ` Jan Beulich
2012-08-03 11:26 ` Andre Przywara
2012-08-03 11:38 ` Jan Beulich
2012-08-03 13:14 ` Dario Faggioli
2012-08-03 13:52 ` Jan Beulich
2012-08-03 22:42 ` Dan Magenheimer
2012-08-08 7:07 ` Dario Faggioli
2012-08-08 7:43 ` Dario Faggioli
2012-08-03 22:22 ` Dan Magenheimer
2012-08-07 23:49 ` 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=1343913696.4873.7.camel@Solace \
--to=raistlin@linux.it \
--cc=JBeulich@suse.com \
--cc=andre.przywara@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=anil@recoil.org \
--cc=dunlapg@gmail.com \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@intel.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.