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

2020년 7월 17일 (금) 오후 5:32, David Laight 님이 작성: > > From: js1...@gmail.com > > Sent: 15 July 2020 06:05 > > 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. >

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

2020년 7월 17일 (금) 오후 5:15, Vlastimil Babka 님이 작성: > > On 7/17/20 10:10 AM, Vlastimil Babka wrote: > > On 7/17/20 9:29 AM, Joonsoo Kim wrote: > >> 2020년 7월 16일 (목) 오후 4:45, Vlastimil Babka 님이 작성: > >>> > >>> On 7/16/20 9:27 AM, Joonsoo Kim wrote: > >>> > 2020년 7월 15일 (수) 오후 5:24, Vlastimil Babka 님이

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

From: js1...@gmail.com > Sent: 15 July 2020 06:05 > 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. ... > diff --git a/mm/page_alloc.c b/mm/page_alloc.c > index

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

On 7/17/20 10:10 AM, Vlastimil Babka wrote: > On 7/17/20 9:29 AM, Joonsoo Kim wrote: >> 2020년 7월 16일 (목) 오후 4:45, Vlastimil Babka 님이 작성: >>> >>> On 7/16/20 9:27 AM, Joonsoo Kim wrote: >>> > 2020년 7월 15일 (수) 오후 5:24, Vlastimil Babka 님이 작성: >>> >> > /* >>> >> > * get_page_from_freelist goes

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

On 7/17/20 9:29 AM, Joonsoo Kim wrote: > 2020년 7월 16일 (목) 오후 4:45, Vlastimil Babka 님이 작성: >> >> On 7/16/20 9:27 AM, Joonsoo Kim wrote: >> > 2020년 7월 15일 (수) 오후 5:24, Vlastimil Babka 님이 작성: >> >> > /* >> >> > * get_page_from_freelist goes through the zonelist trying to allocate >> >> > * a

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

2020년 7월 16일 (목) 오후 4:45, Vlastimil Babka 님이 작성: > > On 7/16/20 9:27 AM, Joonsoo Kim wrote: > > 2020년 7월 15일 (수) 오후 5:24, Vlastimil Babka 님이 작성: > >> > /* > >> > * get_page_from_freelist goes through the zonelist trying to allocate > >> > * a page. > >> > @@ -3706,6 +3714,8 @@

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

On 7/16/20 9:27 AM, Joonsoo Kim wrote: > 2020년 7월 15일 (수) 오후 5:24, Vlastimil Babka 님이 작성: >> > /* >> > * get_page_from_freelist goes through the zonelist trying to allocate >> > * a page. >> > @@ -3706,6 +3714,8 @@ get_page_from_freelist(gfp_t gfp_mask, unsigned int >> > order, int

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

2020년 7월 15일 (수) 오후 5:24, Vlastimil Babka 님이 작성: > > On 7/15/20 7:05 AM, js1...@gmail.com wrote: > > 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. > > > >

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

On Wed 15-07-20 14:05:26, Joonsoo Kim wrote: > 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

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

On 7/15/20 7:05 AM, js1...@gmail.com wrote: > 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,

[PATCH 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