Messages in this thread | | | Subject | Re: [PATCH v3 5/8] mm/migrate: make a standard migration target allocation function | From | Vlastimil Babka <> | Date | Fri, 3 Jul 2020 17:25:59 +0200 |
| |
On 6/23/20 8:13 AM, js1304@gmail.com wrote: > From: Joonsoo Kim <iamjoonsoo.kim@lge.com> > > There are some similar functions for migration target allocation. Since > there is no fundamental difference, it's better to keep just one rather > than keeping all variants. This patch implements base migration target > allocation function. In the following patches, variants will be converted > to use this function. > > Note that PageHighmem() call in previous function is changed to open-code > "is_highmem_idx()" since it provides more readability. > > Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Provided that the "&= ~__GFP_RECLAIM" line is separated patch as you discussed,
Acked-by: Vlastimil Babka <vbabka@suse.cz>
| |