From: Dario Faggioli <dario.faggioli@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>, Li Yechen <lccycc123@gmail.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Matt Wilson <msw@linux.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Elena Ufimtseva <ufimtseva@gmail.com>
Subject: Re: [PATCH RFC v2 1/7] xen/vNUMA: vNUMA support for PV guests.
Date: Tue, 17 Sep 2013 09:11:18 +0200 [thread overview]
Message-ID: <1379401878.32441.42.camel@Abyss> (raw)
In-Reply-To: <52381B4C02000078000F3DD5@nat28.tlf.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 1580 bytes --]
On mar, 2013-09-17 at 08:05 +0100, Jan Beulich wrote:
> >>> On 17.09.13 at 08:44, Elena Ufimtseva <ufimtseva@gmail.com> wrote:
>
> Please don't top post.
>
> > George, after talking to Dario, I think the max number of physical
> > nodes will not exceed 256. Dario's automatic NUMA
> > placement work with this number and I think it can be easily u8.
> > Unless anyone has other thoughts.
>
> With nr_vnodes being uint16_t, the vnode numbers should be
> too. Limiting them to u8 would possibly be even better, but then
> nr_vnodes would better be unsigned int (perhaps that was the
> case from the beginning, regardless of the types used for the
> arrays).
>
> The pnode array surely can also be uint8_t for the time being,
> considering that there are other places where node IDs are
> limited to 8 bits.
>
All agreed.
> And with struct acpi_table_slit having just 8-bit distances, there's
> no apparent reason why the virtual distances can't be 8 bits too.
>
> But - all this is only for the internal representations. Anything in
> the public interface should be wide enough to allow future
> extension.
>
And, in fact, 'node_to_node_distance' in xen/include/public/sysctl.h
(http://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=xen/include/public/sysctl.h)
is uint32.
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
next prev parent reply other threads:[~2013-09-17 7:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 8:49 [PATCH RFC v2 1/7] xen/vNUMA: vNUMA support for PV guests Elena Ufimtseva
2013-09-13 9:31 ` Andrew Cooper
2013-09-13 11:53 ` Jan Beulich
2013-09-13 11:00 ` Jan Beulich
2013-09-16 15:46 ` George Dunlap
2013-09-17 6:44 ` Elena Ufimtseva
2013-09-17 6:59 ` Elena Ufimtseva
2013-09-17 7:05 ` Jan Beulich
2013-09-17 7:11 ` Dario Faggioli [this message]
2013-09-17 7:19 ` Elena Ufimtseva
2013-09-17 9:04 ` Dario Faggioli
2013-10-03 12:27 ` Li Yechen
2013-10-03 15:17 ` Dario Faggioli
2013-10-03 15:33 ` 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=1379401878.32441.42.camel@Abyss \
--to=dario.faggioli@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.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.