RFC migrate: convert migrate_pages()/unmap_and_move() to use folios
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 4 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | migrate: convert unmap_and_move() to use foliosmm/ | +27 | 2 replies | |
| 2/2 | migrate: convert migrate_pages() to use foliosmm/ | +108 | 2 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC 0/2] migrate: convert migrate_pages()/unmap_and_move() to use folios
The conversion is quite straightforward, just replace the page API to the corresponding folio API. migrate_pages() and unmap_and_move() mostly work with folios (head pages) only.
One question is about THP. Which is converted to large folio in the patchset. This is generally OK, because the code can work with arbitrary order large folio at most times. But some THP related statistics (such as THP_MIGRATION_SUCCESS, etc.) are converted for large folio with arbitrary order too. Do we really care about the order of large folio? Do we need to be backward compatible strictly?
Best Regards,
Huang, Ying