From: Dario Faggioli <dario.faggioli@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Keir Fraser <keir@xen.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
George Dunlap <george.dunlap@eu.citrix.com>,
Matt Wilson <msw@linux.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jan Beulich <JBeulich@suse.com>,
Elena Ufimtseva <ufimtseva@gmail.com>
Subject: Re: [PATCH v10 9/9] libxl: vnuma topology configuration parser and doc
Date: Fri, 12 Sep 2014 11:59:02 +0200 [thread overview]
Message-ID: <1410515942.3531.3.camel@Solace.lan> (raw)
In-Reply-To: <20140912093100.GD31343@zion.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1083 bytes --]
On ven, 2014-09-12 at 10:31 +0100, Wei Liu wrote:
> On Fri, Sep 12, 2014 at 11:02:30AM +0200, Dario Faggioli wrote:
> > If, with 'memory ranges', you mean the possibility of specifying
> > different memory size for each node, I think I'd keep this.
> >
> > In fact, bbout memory, I'm fine with how you right now deal with
> > vnuma_mem (which I suggested to rename to "vnuma_memory" or
> > "vnuma_maxmem"), i.e.:
> >
>
> I don't thin vnuma_maxmem reflects what this parameter means. The list
> controls distribution of memory not the maximum amount. The sum of this
> list should be equal to maxmem= in config file.
>
I think you're right. And until we won't have NUMA aware ballooning,
what the maximum amount is will be a bit fuzzy! :-P
So, "vnuma_memory" it is, then. :-)
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: 181 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:[~2014-09-12 9:59 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 4:24 [PATCH v10 3/9] vnuma hook to debug-keys u Elena Ufimtseva
2014-09-03 4:24 ` [PATCH v10 4/9] libxc: Introduce xc_domain_setvnuma to set vNUMA Elena Ufimtseva
2014-09-03 14:53 ` Ian Campbell
2014-09-03 4:24 ` [PATCH v10 5/9] libxl: vnuma types declararion Elena Ufimtseva
2014-09-03 15:03 ` Ian Campbell
2014-09-03 16:04 ` Ian Campbell
2014-09-04 3:48 ` Elena Ufimtseva
[not found] ` <1409826927.15057.22.camel@kazak.uk.xensource.com>
2014-09-08 16:13 ` Dario Faggioli
2014-09-08 19:47 ` Elena Ufimtseva
2014-09-16 6:17 ` Elena Ufimtseva
2014-09-16 7:16 ` Dario Faggioli
2014-09-16 12:57 ` Elena Ufimtseva
2014-09-03 4:24 ` [PATCH v10 6/9] libxl: build numa nodes memory blocks Elena Ufimtseva
2014-09-03 15:21 ` Ian Campbell
2014-09-04 4:47 ` Elena Ufimtseva
2014-09-05 3:50 ` Elena Ufimtseva
2014-09-12 10:18 ` Dario Faggioli
2014-09-03 4:24 ` [PATCH v10 7/9] libxc: allocate domain memory for vnuma enabled Elena Ufimtseva
2014-09-03 15:26 ` Ian Campbell
2014-09-12 11:06 ` Dario Faggioli
2014-09-03 4:24 ` [PATCH v10 8/9] libxl: vnuma nodes placement bits Elena Ufimtseva
2014-09-03 15:50 ` Konrad Rzeszutek Wilk
2014-09-03 15:52 ` Ian Campbell
2014-09-12 16:51 ` Dario Faggioli
2014-09-03 4:24 ` [PATCH v10 9/9] libxl: vnuma topology configuration parser and doc Elena Ufimtseva
2014-09-03 15:42 ` Konrad Rzeszutek Wilk
2014-09-11 17:13 ` Dario Faggioli
2014-09-12 2:04 ` Elena Ufimtseva
2014-09-12 9:02 ` Dario Faggioli
2014-09-12 9:31 ` Wei Liu
2014-09-12 9:59 ` Dario Faggioli [this message]
2014-09-03 15:37 ` [PATCH v10 3/9] vnuma hook to debug-keys u Konrad Rzeszutek Wilk
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=1410515942.3531.3.camel@Solace.lan \
--to=dario.faggioli@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=msw@linux.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=ufimtseva@gmail.com \
--cc=wei.liu2@citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).