Re: [PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-21 Thread Vlastimil Babka
On 01/20/2015 10:08 AM, Vlastimil Babka wrote: > On 01/20/2015 06:52 AM, Aneesh Kumar K.V wrote: >> Vlastimil Babka writes: >> >> is that check correct ? ie, >> >> if ((gfp & GFP_TRANSHUGE) == GFP_TRANSHUGE) >> >> may not always indicate transparent hugepage if defrag = 0 . With defrag >>

Re: [PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-21 Thread Vlastimil Babka
On 01/20/2015 10:08 AM, Vlastimil Babka wrote: On 01/20/2015 06:52 AM, Aneesh Kumar K.V wrote: Vlastimil Babka vba...@suse.cz writes: is that check correct ? ie, if ((gfp GFP_TRANSHUGE) == GFP_TRANSHUGE) may not always indicate transparent hugepage if defrag = 0 . With defrag

Re: [PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-20 Thread Vlastimil Babka
On 01/20/2015 06:52 AM, Aneesh Kumar K.V wrote: > Vlastimil Babka writes: > >> On 01/17/2015 01:02 AM, Andrew Morton wrote: >>> On Fri, 16 Jan 2015 12:56:36 +0530 "Aneesh Kumar K.V" >>> wrote: >>> This make sure that we try to allocate hugepages from local node if allowed by

Re: [PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-20 Thread Vlastimil Babka
On 01/20/2015 06:52 AM, Aneesh Kumar K.V wrote: Vlastimil Babka vba...@suse.cz writes: On 01/17/2015 01:02 AM, Andrew Morton wrote: On Fri, 16 Jan 2015 12:56:36 +0530 Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com wrote: This make sure that we try to allocate hugepages from local node

Re: [PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-19 Thread Aneesh Kumar K.V
Vlastimil Babka writes: > On 01/17/2015 01:02 AM, Andrew Morton wrote: >> On Fri, 16 Jan 2015 12:56:36 +0530 "Aneesh Kumar K.V" >> wrote: >> >>> This make sure that we try to allocate hugepages from local node if >>> allowed by mempolicy. If we can't, we fallback to small page allocation >>>

Re: [PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-19 Thread Vlastimil Babka
On 01/17/2015 01:02 AM, Andrew Morton wrote: > On Fri, 16 Jan 2015 12:56:36 +0530 "Aneesh Kumar K.V" > wrote: > >> This make sure that we try to allocate hugepages from local node if >> allowed by mempolicy. If we can't, we fallback to small page allocation >> based on mempolicy. This is based

Re: [PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-19 Thread Aneesh Kumar K.V
Vlastimil Babka vba...@suse.cz writes: On 01/17/2015 01:02 AM, Andrew Morton wrote: On Fri, 16 Jan 2015 12:56:36 +0530 Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com wrote: This make sure that we try to allocate hugepages from local node if allowed by mempolicy. If we can't, we fallback

Re: [PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-19 Thread Vlastimil Babka
On 01/17/2015 01:02 AM, Andrew Morton wrote: On Fri, 16 Jan 2015 12:56:36 +0530 Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com wrote: This make sure that we try to allocate hugepages from local node if allowed by mempolicy. If we can't, we fallback to small page allocation based on

Re: [PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-18 Thread Aneesh Kumar K.V
Davidlohr Bueso writes: > On Fri, 2015-01-16 at 16:02 -0800, Andrew Morton wrote: >> On Fri, 16 Jan 2015 12:56:36 +0530 "Aneesh Kumar K.V" >> wrote: >> >> > This make sure that we try to allocate hugepages from local node if >> > allowed by mempolicy. If we can't, we fallback to small page

Re: [PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-18 Thread Aneesh Kumar K.V
Andrew Morton writes: > On Fri, 16 Jan 2015 12:56:36 +0530 "Aneesh Kumar K.V" > wrote: > >> This make sure that we try to allocate hugepages from local node if >> allowed by mempolicy. If we can't, we fallback to small page allocation >> based on mempolicy. This is based on the observation

Re: [PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-18 Thread Aneesh Kumar K.V
Andrew Morton a...@linux-foundation.org writes: On Fri, 16 Jan 2015 12:56:36 +0530 Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com wrote: This make sure that we try to allocate hugepages from local node if allowed by mempolicy. If we can't, we fallback to small page allocation based on

Re: [PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-18 Thread Aneesh Kumar K.V
Davidlohr Bueso d...@stgolabs.net writes: On Fri, 2015-01-16 at 16:02 -0800, Andrew Morton wrote: On Fri, 16 Jan 2015 12:56:36 +0530 Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com wrote: This make sure that we try to allocate hugepages from local node if allowed by mempolicy. If we

Re: [PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-16 Thread Davidlohr Bueso
On Fri, 2015-01-16 at 16:02 -0800, Andrew Morton wrote: > On Fri, 16 Jan 2015 12:56:36 +0530 "Aneesh Kumar K.V" > wrote: > > > This make sure that we try to allocate hugepages from local node if > > allowed by mempolicy. If we can't, we fallback to small page allocation > > based on mempolicy.

Re: [PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-16 Thread Andrew Morton
On Fri, 16 Jan 2015 12:56:36 +0530 "Aneesh Kumar K.V" wrote: > This make sure that we try to allocate hugepages from local node if > allowed by mempolicy. If we can't, we fallback to small page allocation > based on mempolicy. This is based on the observation that allocating pages > on local

Re: [PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-16 Thread Vlastimil Babka
On 01/16/2015 08:26 AM, Aneesh Kumar K.V wrote: > This make sure that we try to allocate hugepages from local node if > allowed by mempolicy. If we can't, we fallback to small page allocation > based on mempolicy. This is based on the observation that allocating pages > on local node is more

Re: [PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-16 Thread Kirill A. Shutemov
On Fri, Jan 16, 2015 at 12:56:36PM +0530, Aneesh Kumar K.V wrote: > This make sure that we try to allocate hugepages from local node if > allowed by mempolicy. If we can't, we fallback to small page allocation > based on mempolicy. This is based on the observation that allocating pages > on local

Re: [PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-16 Thread Vlastimil Babka
On 01/16/2015 08:26 AM, Aneesh Kumar K.V wrote: This make sure that we try to allocate hugepages from local node if allowed by mempolicy. If we can't, we fallback to small page allocation based on mempolicy. This is based on the observation that allocating pages on local node is more

Re: [PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-16 Thread Andrew Morton
On Fri, 16 Jan 2015 12:56:36 +0530 Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com wrote: This make sure that we try to allocate hugepages from local node if allowed by mempolicy. If we can't, we fallback to small page allocation based on mempolicy. This is based on the observation that

Re: [PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-16 Thread Davidlohr Bueso
On Fri, 2015-01-16 at 16:02 -0800, Andrew Morton wrote: On Fri, 16 Jan 2015 12:56:36 +0530 Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com wrote: This make sure that we try to allocate hugepages from local node if allowed by mempolicy. If we can't, we fallback to small page allocation

Re: [PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-16 Thread Kirill A. Shutemov
On Fri, Jan 16, 2015 at 12:56:36PM +0530, Aneesh Kumar K.V wrote: This make sure that we try to allocate hugepages from local node if allowed by mempolicy. If we can't, we fallback to small page allocation based on mempolicy. This is based on the observation that allocating pages on local node

[PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-15 Thread Aneesh Kumar K.V
This make sure that we try to allocate hugepages from local node if allowed by mempolicy. If we can't, we fallback to small page allocation based on mempolicy. This is based on the observation that allocating pages on local node is more beneficial than allocating hugepages on remote node.

[PATCH V3] mm/thp: Allocate transparent hugepages on local node

2015-01-15 Thread Aneesh Kumar K.V
This make sure that we try to allocate hugepages from local node if allowed by mempolicy. If we can't, we fallback to small page allocation based on mempolicy. This is based on the observation that allocating pages on local node is more beneficial than allocating hugepages on remote node.