From: George Dunlap <george.dunlap@eu.citrix.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: keir@xen.org, JBeulich@suse.com,
stefano.stabellini@eu.citrix.com, msw@linux.com,
lccycc123@gmail.com, xen-devel@lists.xen.org,
Elena Ufimtseva <ufimtseva@gmail.com>
Subject: Re: [PATCH v2 1/7] xen: vNUMA support for guests.
Date: Thu, 14 Nov 2013 21:43:52 +0000 [thread overview]
Message-ID: <52854418.8050405@eu.citrix.com> (raw)
In-Reply-To: <1384427912.29902.114.camel@Abyss>
On 11/14/2013 11:18 AM, Dario Faggioli wrote:
>> diff --git a/xen/include/xen/domain.h b/xen/include/xen/domain.h
>> index a057069..bc61bab 100644
>> --- a/xen/include/xen/domain.h
>> +++ b/xen/include/xen/domain.h
>> @@ -89,4 +89,14 @@ extern unsigned int xen_processor_pmbits;
>>
>> extern bool_t opt_dom0_vcpus_pin;
>>
>> +struct domain_vnuma_info {
>> + uint nr_vnodes;
>> + uint *vdistance;
>> + uint *vcpu_to_vnode;
>> + uint *vnode_numamap;
>> + struct vmemrange *vmemrange;
>> +};
>> +
> I think you can kill the 'domain_' prefix. It's pretty clear this is a
> per-domain thing, from the fact that it lives inside struct domain.
Still, it doesn't hurt to have a little bit of extra context. If you
look above in this file, for example, it has "vcpu_guest_context" --
even though it should be obvious that guest context is per-vcpu. :-)
>
>> +void domain_vnuma_destroy(struct domain_vnuma_info *v);
>> +
> Why do you need to declare this function here? Isn't this used only in
> domain.c ?
In fact, it should probably be static.
-George
next prev parent reply other threads:[~2013-11-14 21:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 3:26 [PATCH v2 1/7] xen: vNUMA support for guests Elena Ufimtseva
2013-11-14 11:18 ` Dario Faggioli
2013-11-14 21:43 ` George Dunlap [this message]
2013-11-15 8:28 ` Jan Beulich
2013-11-14 11:48 ` David Vrabel
2013-11-14 12:11 ` Dario Faggioli
2013-11-14 14:09 ` Elena Ufimtseva
2013-11-14 21:59 ` George Dunlap
2013-11-14 22:51 ` Elena Ufimtseva
2013-11-14 23:51 ` George Dunlap
2013-11-15 8:50 ` Jan Beulich
2013-11-15 14:14 ` 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=52854418.8050405@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=dario.faggioli@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.