2020년 6월 25일 (목) 오후 9:08, Michal Hocko <mhocko@xxxxxxxxxx>님이 작성: > > On Tue 23-06-20 15:13:46, Joonsoo Kim wrote: > > From: Joonsoo Kim <iamjoonsoo.kim@xxxxxxx> > > > > 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. > > We already can express that by a missing __GFP_MOVABLE so I would rather > not introduce a duplication in form of another flag. I replied to this question in a previous email. Thanks.
