RFC mm: pagewalk: Rework callback return values and optionally skip the pte level
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest4 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | mm: Have the mempolicy pagewalk to avoid positive callback return codesmm/ | +8 | 1 reply | |
| 2/4 | fs: task_mmu: Have the pagewalk avoid positive callback return codesfs/ | +1 | 0 replies | |
| 3/4 | mm: pagewalk: Disallow user positive callback return values and use them for walk controlinclude/ mm/ | +12 | 0 replies | |
| 4/4 | mm: mapping_dirty_helpers: Handle huge pmds correctlymm/ | +10 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/4] mm: pagewalk: Rework callback return values and optionally skip the pte level
This series converts all users of pagewalk positive callback return values to use negative values instead, so that the positive values are free for pagewalk control. Then the return value PAGE_WALK_CONTINUE is introduced. That value is intended for callbacks to indicate that they've handled the entry and it's not necessary to split and go to a lower level. Initially this is implemented only for pmd_entry(), but could (should?) at some point be used also for pud_entry().
Finally the mapping_dirty_helpers pagewalk is modified to use the new value indicating that it has processed a read-only huge pmd entry and don't want it to be split and handled at the pte level.
Note: This series still needs some significant testing and another re-audit to verify that there are no more pagewalk users relying on positive return values.