The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: use BITS_PER_LONG to unify the definition in page->flags
Date: Sun, 19 Mar 2017 10:30:13 -0400	[thread overview]
Message-ID: <20170319143012.GB12414@dhcp22.suse.cz> (raw)
In-Reply-To: <20170318003914.24839-1-richard.weiyang@gmail.com>

On Sat 18-03-17 08:39:14, Wei Yang wrote:
> The field page->flags is defined as unsigned long and is divided into
> several parts to store different information of the page, like section,
> node, zone. Which means all parts must sit in the one "unsigned
> long".
> 
> BITS_PER_LONG is used in several places to ensure this applies.
> 
>     #if SECTIONS_WIDTH+NODES_WIDTH+ZONES_WIDTH > BITS_PER_LONG - NR_PAGEFLAGS
>     #if SECTIONS_WIDTH+ZONES_WIDTH+NODES_SHIFT <= BITS_PER_LONG - NR_PAGEFLAGS
>     #if SECTIONS_WIDTH+ZONES_WIDTH+NODES_SHIFT+LAST_CPUPID_SHIFT <= BITS_PER_LONG - NR_PAGEFLAGS
> 
> While we use "sizeof(unsigned long) * 8" in the definition of
> SECTIONS_PGOFF
> 
>     #define SECTIONS_PGOFF         ((sizeof(unsigned long)*8) - SECTIONS_WIDTH)
> 
> This may not be that obvious for audience to catch the point.
> 
> This patch replaces the "sizeof(unsigned long) * 8" with BITS_PER_LONG to
> make all this consistent.

I am not really sure this is an improvement. page::flags is unsigned
long nad the current code reflects that type.

> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
> ---
>  include/linux/mm.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/mm.h b/include/linux/mm.h
> index b84615b0f64c..a5d80de089ff 100644
> --- a/include/linux/mm.h
> +++ b/include/linux/mm.h
> @@ -684,7 +684,7 @@ int finish_mkwrite_fault(struct vm_fault *vmf);
>   */
>  
>  /* Page flags: | [SECTION] | [NODE] | ZONE | [LAST_CPUPID] | ... | FLAGS | */
> -#define SECTIONS_PGOFF		((sizeof(unsigned long)*8) - SECTIONS_WIDTH)
> +#define SECTIONS_PGOFF		(BITS_PER_LONG - SECTIONS_WIDTH)
>  #define NODES_PGOFF		(SECTIONS_PGOFF - NODES_WIDTH)
>  #define ZONES_PGOFF		(NODES_PGOFF - ZONES_WIDTH)
>  #define LAST_CPUPID_PGOFF	(ZONES_PGOFF - LAST_CPUPID_WIDTH)
> -- 
> 2.11.0
> 

-- 
Michal Hocko
SUSE Labs

  reply	other threads:[~2017-03-19 14:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-18  0:39 [PATCH] mm: use BITS_PER_LONG to unify the definition in page->flags Wei Yang
2017-03-19 14:30 ` Michal Hocko [this message]
2017-03-19 15:03   ` Wei Yang
2017-03-19 15:08     ` Michal Hocko
2017-03-19 16:05       ` Wei Yang

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=20170319143012.GB12414@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=richard.weiyang@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox