From: George Dunlap <George.Dunlap@eu.citrix.com>
To: Elena Ufimtseva <ufimtseva@gmail.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Dario Faggioli <dario.faggioli@citrix.com>,
Li Yechen <lccycc123@gmail.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
sw@linux.com
Subject: Re: [PATCH RFC v2 5/7] libxl/vNUMA: VM config parsing functions
Date: Thu, 19 Sep 2013 15:29:00 +0100 [thread overview]
Message-ID: <CAFLBxZbqsUDOXjoajD4NoGs7qOt5OaRHzJ8JBFGLiy9a-VxbSg@mail.gmail.com> (raw)
In-Reply-To: <1379062224-13894-1-git-send-email-ufimtseva@gmail.com>
On Fri, Sep 13, 2013 at 9:50 AM, Elena Ufimtseva <ufimtseva@gmail.com> wrote:
> vNUMA VM config parsing functions.
> Parses VM vNUMA related config, verifies and
> sets default values for errorneous parameters.
> If sum of all vnodes memory sizes does not match
> memory, it will be adjusted accordingly;
Also:
* I think if there's a mismatch in the config file we should error
out, not allow one bit of the config to override another part.
* It's probably worth making a default for vnumamem as well, as there
is for vcpu_to_vnode.
-George
next prev parent reply other threads:[~2013-09-19 14:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 8:50 [PATCH RFC v2 5/7] libxl/vNUMA: VM config parsing functions Elena Ufimtseva
2013-09-19 14:09 ` George Dunlap
2013-09-19 14:29 ` George Dunlap [this message]
2013-10-09 18:45 ` Elena Ufimtseva
2013-10-10 8:38 ` Dario Faggioli
2013-10-10 16:25 ` Elena Ufimtseva
2013-10-10 21:32 ` Dario Faggioli
2013-10-10 22:32 ` Elena Ufimtseva
2013-10-11 11:18 ` Ian Jackson
2013-10-14 13:15 ` Dario Faggioli
2013-10-14 13:26 ` Ian Jackson
2013-10-14 16:52 ` Elena Ufimtseva
2013-10-14 16:45 ` 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=CAFLBxZbqsUDOXjoajD4NoGs7qOt5OaRHzJ8JBFGLiy9a-VxbSg@mail.gmail.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=lccycc123@gmail.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=sw@linux.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 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).