All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: kevin.tian@intel.com, keir@xen.org, ian.campbell@citrix.com,
	Andrew.Cooper3@citrix.com, dario.faggioli@citrix.com,
	tim@xen.org, xen-devel@lists.xen.org,
	stefano.stabellini@citrix.com, yang.z.zhang@intel.com
Subject: Re: [PATCH v2 3/3] mm: MEMF_node should handle changes in nodeid_t size
Date: Wed, 25 Feb 2015 08:30:13 -0500	[thread overview]
Message-ID: <54EDCE65.203@oracle.com> (raw)
In-Reply-To: <54EDB39D02000078000637BE@mail.emea.novell.com>

On 02/25/2015 05:35 AM, Jan Beulich wrote:
>>>> On 24.02.15 at 20:11, <boris.ostrovsky@oracle.com> wrote:
>> @@ -121,10 +123,12 @@ struct npfec {
>>   #define _MEMF_exact_node  4
>>   #define  MEMF_exact_node  (1U<<_MEMF_exact_node)
>>   #define _MEMF_node        8
>> -#define  MEMF_node(n)     ((((n)+1)&0xff)<<_MEMF_node)
>> +#define  MEMF_node(n)     ((((n)+1) & MEMF_node_mask) << _MEMF_node)
>>   #define _MEMF_bits        24
>>   #define  MEMF_bits(n)     ((n)<<_MEMF_bits)
>>   
>> +#define MEMF2NODE(memflags) (MASK_EXTR(memflags, MEMF_node_mask) - 1)
> As this is being used just once, I don't really see a need for it to be
> exposed globally. Perhaps do away with the macro, but at the very
> least confine it to page_alloc.c.

I intentionally put it here: we have macro to encode ('put', so to 
speak) nodeID in memflags in this file (by adding one to it) and so I 
felt that we don't need to expose this encoding outside of this file by 
providing a "get" macro.

-boris

  reply	other threads:[~2015-02-25 13:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 19:11 [PATCH v2 0/3] Updates to pxm2node mapping and nodeID sizing Boris Ostrovsky
2015-02-24 19:11 ` [PATCH v2 1/3] x86/numa: Allow arbitrary value of PXM in PXM<->node mapping Boris Ostrovsky
2015-02-24 20:58   ` Boris Ostrovsky
2015-02-25  9:34   ` Jan Beulich
2015-02-25 13:11     ` Boris Ostrovsky
2015-02-25 13:25       ` Jan Beulich
2015-02-25 10:34   ` Jan Beulich
2015-02-24 19:11 ` [PATCH v2 2/3] x86/numa: Adjust datatypes for node and pxm Boris Ostrovsky
2015-02-25  9:44   ` Jan Beulich
2015-02-24 19:11 ` [PATCH v2 3/3] mm: MEMF_node should handle changes in nodeid_t size Boris Ostrovsky
2015-02-25  9:47   ` Jan Beulich
2015-02-25 10:35   ` Jan Beulich
2015-02-25 13:30     ` Boris Ostrovsky [this message]
2015-02-25 14:16       ` Jan Beulich

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=54EDCE65.203@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=dario.faggioli@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=keir@xen.org \
    --cc=kevin.tian@intel.com \
    --cc=stefano.stabellini@citrix.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.