2020년 7월 4일 (토) 오전 12:56, Vlastimil Babka 님이 작성:
>
> On 6/23/20 8:13 AM, js1...@gmail.com wrote:
> > From: Joonsoo Kim
> >
> > There is a well-defined migration target allocation callback.
> > It's mostly similar with new_non_cma_page() except considering CMA pages.
> >
> > This patch adds a CMA c
On 6/23/20 8:13 AM, js1...@gmail.com wrote:
> From: Joonsoo Kim
>
> There is a well-defined migration target allocation callback.
> It's mostly similar with new_non_cma_page() except considering CMA pages.
>
> This patch adds a CMA consideration to the standard migration target
> allocation call
2020년 6월 25일 (목) 오후 9:08, Michal Hocko 님이 작성:
>
> On Tue 23-06-20 15:13:46, Joonsoo Kim wrote:
> > From: Joonsoo Kim
> >
> > There is a well-defined migration target allocation callback.
> > It's mostly similar with new_non_cma_page() except considering CMA pages.
> >
> > This patch adds a CMA con
On Tue 23-06-20 15:13:46, Joonsoo Kim wrote:
> From: Joonsoo Kim
>
> There is a well-defined migration target allocation callback.
> It's mostly similar with new_non_cma_page() except considering CMA pages.
>
> This patch adds a CMA consideration to the standard migration target
> allocation cal
From: Joonsoo Kim
There is a well-defined migration target allocation callback.
It's mostly similar with new_non_cma_page() except considering CMA pages.
This patch adds a CMA consideration to the standard migration target
allocation callback and use it on gup.c.
Signed-off-by: Joonsoo Kim
---
5 matches
Mail list logo