[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170726100718.GG2981@dhcp22.suse.cz>
Date: Wed, 26 Jul 2017 12:07:18 +0200
From: Michal Hocko <mhocko@...nel.org>
To: Mike Kravetz <mike.kravetz@...cle.com>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Matthew Wilcox <willy@...radead.org>,
akpm@...ux-foundation.org, ak@...ux.intel.com,
mtk.manpages@...il.com, Davidlohr Bueso <dbueso@...e.de>,
khandual@...ux.vnet.ibm.com, aneesh.kumar@...ux.vnet.ibm.com,
aarcange@...hat.com
Subject: Re: [RFC PATCH 3/3] mm: shm: Use new hugetlb size encoding
definitions
On Wed 26-07-17 11:53:38, Michal Hocko wrote:
> On Mon 17-07-17 15:28:01, Mike Kravetz wrote:
> > Use the common definitions from hugetlb_encode.h header file for
> > encoding hugetlb size definitions in shmget system call flags. In
> > addition, move these definitions to the from the internal to user
> > (uapi) header file.
>
> s@to the from@...m@
>
> >
> > Suggested-by: Matthew Wilcox <willy@...radead.org>
> > Signed-off-by: Mike Kravetz <mike.kravetz@...cle.com>
>
> with s@...ETLB_FLAG_ENCODE__16GB@...ETLB_FLAG_ENCODE_16GB@
>
> Acked-by: Michal Hocko <mhocko@...e.com>
Btw. man page mentions only 2MB and 1GB, we should document others and
note that each arch might support only subset of them
> > +#define MAP_HUGE_512KB HUGETLB_FLAG_ENCODE_512KB
> > +#define MAP_HUGE_1MB HUGETLB_FLAG_ENCODE_1MB
> > +#define MAP_HUGE_2MB HUGETLB_FLAG_ENCODE_2MB
> > +#define MAP_HUGE_8MB HUGETLB_FLAG_ENCODE_8MB
> > +#define MAP_HUGE_16MB HUGETLB_FLAG_ENCODE_16MB
> > +#define MAP_HUGE_1GB HUGETLB_FLAG_ENCODE_1GB
> > +#define MAP_HUGE_16GB HUGETLB_FLAG_ENCODE__16GB
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists