From: Ian Campbell <Ian.Campbell@citrix.com>
To: Elena Ufimtseva <ufimtseva@gmail.com>
Cc: keir@xen.org, stefano.stabellini@eu.citrix.com,
george.dunlap@eu.citrix.com, msw@linux.com,
dario.faggioli@citrix.com, lccycc123@gmail.com,
ian.jackson@eu.citrix.com, xen-devel@lists.xen.org,
JBeulich@suse.com
Subject: Re: [PATCH v10 8/9] libxl: vnuma nodes placement bits
Date: Wed, 3 Sep 2014 16:52:16 +0100 [thread overview]
Message-ID: <1409759536.3323.39.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <1409718258-3276-6-git-send-email-ufimtseva@gmail.com>
On Wed, 2014-09-03 at 00:24 -0400, Elena Ufimtseva wrote:
> + /* default setting. */
> + for (i = 0; i < info->vnodes; i++)
> + info->vnuma_vnodemap[i] = LIBXC_VNUMA_NO_NODE;
What if the user had specified this?
> +static int libxl__build_vnuma_ranges(libxl__gc *gc,
> + uint32_t domid,
> + /* IN: mem sizes in megabytes */
> + libxl_domain_build_info *b_info,
const please.
> + /* OUT: linux NUMA blocks addresses */
More Linux specifics.
> + vmemrange_t **memrange)
> +{
> + /*
> + * For non-PV domains, contruction of the regions will
"construction"
> + b_info->vmemranges = b_info->vnodes;
What if the user had specified vmemranges themselves?
Actually, I'm becomign increasingly confused about the fields in the
libxl interface, so I think I'm going to go back to patch #5 to clarify
that before I try to understand any more of this code.
Ian.
next prev parent reply other threads:[~2014-09-03 15:52 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 [this message]
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
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=1409759536.3323.39.camel@kazak.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=lccycc123@gmail.com \
--cc=msw@linux.com \
--cc=stefano.stabellini@eu.citrix.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.