All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <raistlin@linux.it>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Andre Przywara <andre.przywara@amd.com>,
	Anil Madhavapeddy <anil@recoil.org>,
	George Dunlap <dunlapg@gmail.com>,
	xen-devel <xen-devel@lists.xen.org>,
	Jan Beulich <JBeulich@suse.com>,
	"Zhang, Yang Z" <yang.z.zhang@intel.com>
Subject: Re: NUMA TODO-list for xen-devel
Date: Wed, 01 Aug 2012 18:47:14 +0200	[thread overview]
Message-ID: <1343839634.4958.39.camel@Solace> (raw)
In-Reply-To: <501959BE.60801@citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 1738 bytes --]

On Wed, 2012-08-01 at 17:30 +0100, Andrew Cooper wrote:
> On 01/08/12 17:16, Dario Faggioli wrote:
>
> ...
>
> > - Automatic placement at guest creation time. Basics are there and
> > will be shipping with 4.2. However, a lot of other things are
> > missing and/or can be improved, for instance:
> > [D] * automated verification and testing of the placement;
> > * benchmarks and improvements of the placement heuristic;
> > [D] * choosing/building up some measure of node load (more accurate
> > than just counting vcpus) onto which to rely during placement;
> > * consider IONUMA during placement;
> > * automatic placement of Dom0, if possible (my current series is
> > only affecting DomU)
> > * having internal xen data structure honour the placement (e.g., 
> > I've been told that right now vcpu stacks are always allocated
> > on node 0... Andrew?).
> >
> 
> - 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.

As you see, I already tried to consider that (as you told me it does
that couple of weeks ago :-) ). I'll add your wording of it (much better
than mine) to the wiki... I understand you're working on this, aren't
you? Can I put that down to?

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

  reply	other threads:[~2012-08-01 16:47 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 [this message]
2012-08-01 16:53     ` Andrew Cooper
2012-08-02  9:40   ` Jan Beulich
2012-08-02 13:21     ` Dario Faggioli
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=1343839634.4958.39.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.