Re: [PATCH 1/2] mm/slub: wake up kswapd for initial high order allocation

On Wed 06-09-17 10:59:09, Cristopher Lameter wrote: > On Wed, 6 Sep 2017, js1...@gmail.com wrote: > > > --- a/mm/slub.c > > +++ b/mm/slub.c > > @@ -1578,8 +1578,12 @@ static struct page *allocate_slab(struct kmem_cache > > *s, gfp_t flags, int node) > > * so we fall-back to the minimum

Re: [PATCH 1/2] mm/slub: wake up kswapd for initial high order allocation

On Wed 06-09-17 10:59:09, Cristopher Lameter wrote: > On Wed, 6 Sep 2017, js1...@gmail.com wrote: > > > --- a/mm/slub.c > > +++ b/mm/slub.c > > @@ -1578,8 +1578,12 @@ static struct page *allocate_slab(struct kmem_cache > > *s, gfp_t flags, int node) > > * so we fall-back to the minimum

Re: [PATCH 1/2] mm/slub: wake up kswapd for initial high order allocation

On Wed, 6 Sep 2017, js1...@gmail.com wrote: > --- a/mm/slub.c > +++ b/mm/slub.c > @@ -1578,8 +1578,12 @@ static struct page *allocate_slab(struct kmem_cache > *s, gfp_t flags, int node) >* so we fall-back to the minimum order allocation. >*/ > alloc_gfp = (flags |

Re: [PATCH 1/2] mm/slub: wake up kswapd for initial high order allocation

On Wed, 6 Sep 2017, js1...@gmail.com wrote: > --- a/mm/slub.c > +++ b/mm/slub.c > @@ -1578,8 +1578,12 @@ static struct page *allocate_slab(struct kmem_cache > *s, gfp_t flags, int node) >* so we fall-back to the minimum order allocation. >*/ > alloc_gfp = (flags |

Re: [PATCH 1/2] mm/slub: wake up kswapd for initial high order allocation

On 09/06/2017 06:37 AM, js1...@gmail.com wrote: > From: Joonsoo Kim > > slub uses higher order allocation than it actually needs. In this case, > we don't want to do direct reclaim to make such a high order page since > it causes a big latency to the user. Instead, we

Re: [PATCH 1/2] mm/slub: wake up kswapd for initial high order allocation

On 09/06/2017 06:37 AM, js1...@gmail.com wrote: > From: Joonsoo Kim > > slub uses higher order allocation than it actually needs. In this case, > we don't want to do direct reclaim to make such a high order page since > it causes a big latency to the user. Instead, we would like to fallback >

[PATCH 1/2] mm/slub: wake up kswapd for initial high order allocation

From: Joonsoo Kim slub uses higher order allocation than it actually needs. In this case, we don't want to do direct reclaim to make such a high order page since it causes a big latency to the user. Instead, we would like to fallback lower order allocation that it

[PATCH 1/2] mm/slub: wake up kswapd for initial high order allocation

From: Joonsoo Kim slub uses higher order allocation than it actually needs. In this case, we don't want to do direct reclaim to make such a high order page since it causes a big latency to the user. Instead, we would like to fallback lower order allocation that it actually needs. However, we

Re: [PATCH 1/2] mm/slub: wake up kswapd for initial high order allocation

On 08/29/2017 02:22 AM, Joonsoo Kim wrote: > On Mon, Aug 28, 2017 at 12:04:41PM +0200, Vlastimil Babka wrote: >> >> Hm, so this seems to revert Mel's 444eb2a449ef ("mm: thp: set THP defrag >> by default to madvise and add a stall-free defrag option") wrt the slub >> allocate_slab() part. AFAICS

Re: [PATCH 1/2] mm/slub: wake up kswapd for initial high order allocation

On 08/29/2017 02:22 AM, Joonsoo Kim wrote: > On Mon, Aug 28, 2017 at 12:04:41PM +0200, Vlastimil Babka wrote: >> >> Hm, so this seems to revert Mel's 444eb2a449ef ("mm: thp: set THP defrag >> by default to madvise and add a stall-free defrag option") wrt the slub >> allocate_slab() part. AFAICS

Re: [PATCH 1/2] mm/slub: wake up kswapd for initial high order allocation

On Mon, Aug 28, 2017 at 12:04:41PM +0200, Vlastimil Babka wrote: > On 08/28/2017 03:11 AM, js1...@gmail.com wrote: > > From: Joonsoo Kim > > > > slub uses higher order allocation than it actually needs. In this case, > > we don't want to do direct reclaim to make such a

Re: [PATCH 1/2] mm/slub: wake up kswapd for initial high order allocation

On Mon, Aug 28, 2017 at 12:04:41PM +0200, Vlastimil Babka wrote: > On 08/28/2017 03:11 AM, js1...@gmail.com wrote: > > From: Joonsoo Kim > > > > slub uses higher order allocation than it actually needs. In this case, > > we don't want to do direct reclaim to make such a high order page since > >

Re: [PATCH 1/2] mm/slub: wake up kswapd for initial high order allocation

On 08/28/2017 03:11 AM, js1...@gmail.com wrote: > From: Joonsoo Kim > > slub uses higher order allocation than it actually needs. In this case, > we don't want to do direct reclaim to make such a high order page since > it causes a big latency to the user. Instead, we

Re: [PATCH 1/2] mm/slub: wake up kswapd for initial high order allocation

On 08/28/2017 03:11 AM, js1...@gmail.com wrote: > From: Joonsoo Kim > > slub uses higher order allocation than it actually needs. In this case, > we don't want to do direct reclaim to make such a high order page since > it causes a big latency to the user. Instead, we would like to fallback >

[PATCH 1/2] mm/slub: wake up kswapd for initial high order allocation

From: Joonsoo Kim slub uses higher order allocation than it actually needs. In this case, we don't want to do direct reclaim to make such a high order page since it causes a big latency to the user. Instead, we would like to fallback lower order allocation that it

[PATCH 1/2] mm/slub: wake up kswapd for initial high order allocation

From: Joonsoo Kim slub uses higher order allocation than it actually needs. In this case, we don't want to do direct reclaim to make such a high order page since it causes a big latency to the user. Instead, we would like to fallback lower order allocation that it actually needs. However, we