Re: [PATCH] mm: use BITS_PER_LONG to unify the definition in page->flags

2017-03-19 Thread Wei Yang
On Sun, Mar 19, 2017 at 11:08:22AM -0400, Michal Hocko wrote: >On Sun 19-03-17 23:03:45, Wei Yang wrote: >> On Sun, Mar 19, 2017 at 10:30:13AM -0400, Michal Hocko wrote: >> >On Sat 18-03-17 08:39:14, Wei Yang wrote: >> >> The field page->flags is defined as unsigned long and is divided into >> >>

Re: [PATCH] mm: use BITS_PER_LONG to unify the definition in page->flags

2017-03-19 Thread Wei Yang
On Sun, Mar 19, 2017 at 11:08:22AM -0400, Michal Hocko wrote: >On Sun 19-03-17 23:03:45, Wei Yang wrote: >> On Sun, Mar 19, 2017 at 10:30:13AM -0400, Michal Hocko wrote: >> >On Sat 18-03-17 08:39:14, Wei Yang wrote: >> >> The field page->flags is defined as unsigned long and is divided into >> >>

Re: [PATCH] mm: use BITS_PER_LONG to unify the definition in page->flags

2017-03-19 Thread Michal Hocko
On Sun 19-03-17 23:03:45, Wei Yang wrote: > On Sun, Mar 19, 2017 at 10:30:13AM -0400, Michal Hocko wrote: > >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

Re: [PATCH] mm: use BITS_PER_LONG to unify the definition in page->flags

2017-03-19 Thread Michal Hocko
On Sun 19-03-17 23:03:45, Wei Yang wrote: > On Sun, Mar 19, 2017 at 10:30:13AM -0400, Michal Hocko wrote: > >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

Re: [PATCH] mm: use BITS_PER_LONG to unify the definition in page->flags

2017-03-19 Thread Wei Yang
On Sun, Mar 19, 2017 at 10:30:13AM -0400, Michal Hocko wrote: >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

Re: [PATCH] mm: use BITS_PER_LONG to unify the definition in page->flags

2017-03-19 Thread Wei Yang
On Sun, Mar 19, 2017 at 10:30:13AM -0400, Michal Hocko wrote: >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

Re: [PATCH] mm: use BITS_PER_LONG to unify the definition in page->flags

2017-03-19 Thread Michal Hocko
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

Re: [PATCH] mm: use BITS_PER_LONG to unify the definition in page->flags

2017-03-19 Thread Michal Hocko
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

[PATCH] mm: use BITS_PER_LONG to unify the definition in page->flags

2017-03-17 Thread Wei Yang
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

[PATCH] mm: use BITS_PER_LONG to unify the definition in page->flags

2017-03-17 Thread Wei Yang
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