Re: [PATCH v2] mm/page_alloc: fix memalloc_nocma_{save/restore} APIs

2020-07-23 Thread Joonsoo Kim
2020년 7월 24일 (금) 오후 12:14, Andrew Morton 님이 작성: > > On Fri, 24 Jul 2020 12:04:02 +0900 Joonsoo Kim wrote: > > > 2020년 7월 24일 (금) 오전 11:36, Andrew Morton 님이 작성: > > > > > > On Fri, 24 Jul 2020 11:23:52 +0900 Joonsoo Kim wrote: > > > > > > > > > Second, clearing __GFP_MOVABLE in

Re: [PATCH v2] mm/page_alloc: fix memalloc_nocma_{save/restore} APIs

2020-07-23 Thread Andrew Morton
On Fri, 24 Jul 2020 12:04:02 +0900 Joonsoo Kim wrote: > 2020년 7월 24일 (금) 오전 11:36, Andrew Morton 님이 작성: > > > > On Fri, 24 Jul 2020 11:23:52 +0900 Joonsoo Kim wrote: > > > > > > > Second, clearing __GFP_MOVABLE in current_gfp_context() has a side > > > > > effect > > > > > to exclude the

Re: [PATCH v2] mm/page_alloc: fix memalloc_nocma_{save/restore} APIs

2020-07-23 Thread Joonsoo Kim
2020년 7월 24일 (금) 오전 11:36, Andrew Morton 님이 작성: > > On Fri, 24 Jul 2020 11:23:52 +0900 Joonsoo Kim wrote: > > > > > Second, clearing __GFP_MOVABLE in current_gfp_context() has a side > > > > effect > > > > to exclude the memory on the ZONE_MOVABLE for allocation target. > > > > > > More whoops.

Re: [PATCH v2] mm/page_alloc: fix memalloc_nocma_{save/restore} APIs

2020-07-23 Thread Andrew Morton
On Fri, 24 Jul 2020 11:23:52 +0900 Joonsoo Kim wrote: > > > Second, clearing __GFP_MOVABLE in current_gfp_context() has a side effect > > > to exclude the memory on the ZONE_MOVABLE for allocation target. > > > > More whoops. > > > > Could we please have a description of the end-user-visible

Re: [PATCH v2] mm/page_alloc: fix memalloc_nocma_{save/restore} APIs

2020-07-23 Thread Joonsoo Kim
2020년 7월 24일 (금) 오전 10:08, Andrew Morton 님이 작성: > > On Thu, 23 Jul 2020 10:49:02 +0900 js1...@gmail.com wrote: > > > From: Joonsoo Kim > > > > Currently, memalloc_nocma_{save/restore} API that prevents CMA area > > in page allocation is implemented by using current_gfp_context(). However, > >

Re: [PATCH v2] mm/page_alloc: fix memalloc_nocma_{save/restore} APIs

2020-07-23 Thread Andrew Morton
On Thu, 23 Jul 2020 10:49:02 +0900 js1...@gmail.com wrote: > From: Joonsoo Kim > > Currently, memalloc_nocma_{save/restore} API that prevents CMA area > in page allocation is implemented by using current_gfp_context(). However, > there are two problems of this implementation. > > First, this

[PATCH v2] mm/page_alloc: fix memalloc_nocma_{save/restore} APIs

2020-07-22 Thread js1304
From: Joonsoo Kim Currently, memalloc_nocma_{save/restore} API that prevents CMA area in page allocation is implemented by using current_gfp_context(). However, there are two problems of this implementation. First, this doesn't work for allocation fastpath. In the fastpath, original gfp_mask is