On Sat, 17 Aug 2024 19:58:07 -0400 Zi Yan <ziy@xxxxxxxxxx> wrote: > > Please correct me or help to write better description, thanks. > > How about? > > Gigantic PageHuge is bigger than a pageblock, but since it is freed as order-0 pages, > its pageblocks after being freed will get to the right free list. There is no need > to have special handling code for them in start_isolate_page_range(). For both > alloc_contig_range() and memory offline cases, the migration code after > start_isolate_page_range() will be able to migrate gigantic PageHuge when possible. > Let's clean up start_isolate_page_range() and fix the aforementioned memory offline > failure issue all together. Thanks, I updated the changelog with the above.
