All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Elena Ufimtseva <ufimtseva@gmail.com>
Cc: lccycc123@gmail.com, george.dunlap@eu.citrix.com,
	xen-devel@lists.xen.org, david.vrabel@citrix.com, msw@amazon.com,
	boris.ostrovsky@oracle.com
Subject: Re: [PATCH RFC v2 0/2] linux/vnuma: vNUMA PV guest support introduction
Date: Wed, 18 Sep 2013 18:16:38 +0200	[thread overview]
Message-ID: <1379520998.18543.183.camel@Abyss> (raw)
In-Reply-To: <1379406841-7441-1-git-send-email-ufimtseva@gmail.com>


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

On mar, 2013-09-17 at 04:33 -0400, Elena Ufimtseva wrote:
> This patchset introduces vNUMA for PV domU guest.
> 
I'm picky and I know it, but I think domU and guest are synonyms...
Having just one of them should be enough.

Also, the subject line "linux/vnuma: vNUMA...". It is indeed a good
practice to indicate to what component and subsystem the patches applies
to. However, in this case, I don't think havin "linux/" there adds much,
since you'll be sending these mainly in LKML (although, yes, they'll go
on xen-devel too, but I honestly think we can manage).

Regarding the "/vnuma" part, well, vnuma isn't really a subsystem.
Actually, it does not even exist before this series, so again, I won't
put it there.

Actually, from a Linux developer/maintainer point of view, these patches
are about Xen, so something like "xen:..." or "x86/xen:" is probably
better

> Enables PV guest to discover NUMA topology provided by Xen
> and initializes NUMA topology on boot. XENMEM subop hypercall
> is used to retreive information from Xen. 
>
The fact that this happens during the regular x86 NUMA initialization
phase (i.e., in x86_numa_init()) is worth mentioning here.

> Xen provides number 
> of NUMA nodes, memory regions (start and end pfn) constructed 
> based on e820 domU map, distance table and cpu to node map. i
> xen_numa_init is called to setup NUMA related structures. 
> To enable this mechanism, kernel should be compiled as PV guest
> with CONFIG_NUMA=y and Xen should support vNUMA functionality 
> (patchset http://lists.xenproject.org/archives/html/xen-devel/2013-09/msg01337.html ).
>  
This is fine. Perhaps I'd add something about future plans, which are to
extend this to work for Dom0 too.

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

  parent reply	other threads:[~2013-09-18 16:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17  8:33 [PATCH RFC v2 0/2] linux/vnuma: vNUMA PV guest support introduction Elena Ufimtseva
2013-09-17  8:34 ` [PATCH RFC v2 1/2] linux/vnuma: vNUMA for PV domu guest Elena Ufimtseva
2013-09-17 14:10   ` David Vrabel
2013-09-18  6:16     ` Elena Ufimtseva
2013-09-18  7:17       ` Dario Faggioli
2013-09-18  7:41         ` Elena Ufimtseva
2013-09-18 12:23       ` David Vrabel
2013-09-17 14:21   ` Boris Ostrovsky
2013-09-18  6:30     ` Elena Ufimtseva
2013-09-18  7:33       ` Dario Faggioli
2013-09-18  7:39         ` Elena Ufimtseva
2013-09-18 16:04   ` Dario Faggioli
2013-09-17  8:34 ` [PATCH RFC v2 2/2] linux/vnuma: Enables NUMA for domu PV guest Elena Ufimtseva
2013-09-17 14:17   ` David Vrabel
2013-09-17 14:37     ` Dario Faggioli
2013-09-18  6:32       ` Elena Ufimtseva
2013-09-18 15:14   ` Dario Faggioli
2013-09-27 17:03     ` Konrad Rzeszutek Wilk
2013-09-18 16:16 ` Dario Faggioli [this message]
2013-09-18 16:20   ` [PATCH RFC v2 0/2] linux/vnuma: vNUMA PV guest support introduction Elena Ufimtseva

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=1379520998.18543.183.camel@Abyss \
    --to=dario.faggioli@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=lccycc123@gmail.com \
    --cc=msw@amazon.com \
    --cc=ufimtseva@gmail.com \
    --cc=xen-devel@lists.xen.org \
    /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.