From: Dario Faggioli <dario.faggioli@citrix.com>
To: "boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
"Keir (Xen.org)" <keir@xen.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
"Tim (Xen.org)" <tim@xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Stefano Stabellini <Stefano.Stabellini@citrix.com>,
"jbeulich@suse.com" <jbeulich@suse.com>,
"yang.z.zhang@intel.com" <yang.z.zhang@intel.com>
Subject: Re: [PATCH v3 1/3] x86/numa: Allow arbitrary value of PXM in PXM<->node mapping
Date: Thu, 26 Feb 2015 09:06:22 +0000 [thread overview]
Message-ID: <1424941579.4742.201.camel@citrix.com> (raw)
In-Reply-To: <1424907714-10527-2-git-send-email-boris.ostrovsky@oracle.com>
[-- Attachment #1.1: Type: text/plain, Size: 586 bytes --]
On Wed, 2015-02-25 at 18:41 -0500, Boris Ostrovsky wrote:
> ACPI defines proximity domain identifier as a 32-bit integer. While
> in most cases the values will be zero-based this is not guaranteed,
> making current pxm2node[256] mapping structure not appropriate.
>
> We will instead use MAX_NUMNODES-sized array of struct pxm2node to
> store PXM-to-node mapping. To accommodate common case of zero-based
> and contiguios PXMs we will, whenever possible, try to use PXM as
> index into this array array for fast lookups.
>
^array for fast lookups.
Dario
[-- 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:[~2015-02-26 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 23:41 [PATCH v3 0/3] Updates to pxm2node mapping and nodeID sizing Boris Ostrovsky
2015-02-25 23:41 ` [PATCH v3 1/3] x86/numa: Allow arbitrary value of PXM in PXM<->node mapping Boris Ostrovsky
2015-02-26 8:38 ` Jan Beulich
2015-02-26 9:06 ` Dario Faggioli [this message]
2015-02-25 23:41 ` [PATCH v3 2/3] x86/numa: Adjust datatypes for node and pxm Boris Ostrovsky
2015-02-25 23:41 ` [PATCH v3 3/3] mm: MEMF_node should handle changes in nodeid_t size Boris Ostrovsky
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=1424941579.4742.201.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Stefano.Stabellini@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@intel.com \
/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.