Re: [PATCH v2 1/4] mm/page_alloc: fix non cma alloc context

2020년 7월 21일 (화) 오전 8:23, Andrew Morton 님이 작성: > > On Mon, 20 Jul 2020 13:56:15 +0900 js1...@gmail.com wrote: > > > Currently, preventing cma area in page allocation is implemented by using > > current_gfp_context(). However, there are two problems of this > > implementation. > > > > First, this

Re: [PATCH v2 1/4] mm/page_alloc: fix non cma alloc context

On Mon, 20 Jul 2020 13:56:15 +0900 js1...@gmail.com wrote: > Currently, preventing 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, >

Re: [PATCH v2 1/4] mm/page_alloc: fix non cma alloc context

On Mon, 20 Jul 2020 13:56:15 +0900 js1...@gmail.com wrote: > Currently, preventing 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, >

[PATCH v2 1/4] mm/page_alloc: fix non cma alloc context

From: Joonsoo Kim Currently, preventing 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 used since current_gfp_context() is