High-order per-cpu cache v6
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 3 repliesIn review 1 of 2 applied
Changelog since v5 from the cover letter
o Changelog clarification in patch 1
o Additional comments in patch 2
Patches in v1 1 of 2 applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | mm, page_alloc: Keep pcp count and list contents in sync if struct page is corruptedmm/ | +10 | 3 replies | Applied |
| 2/2 | mm: page_alloc: High-order per-cpu page allocator v6include/ mm/ | +93 | 0 replies |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Vlastimil Babka | Johannes Weiner | Jesper Dangaard Brouer | Michal Hocko | Hillf Danton |
|---|---|---|---|---|---|
| 1/2 | A-b | A-b | A-b | ||
| 2/2 | A-b | A-b | A-b | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 5 reviewers.
Cover letter [PATCH 0/2] High-order per-cpu cache v6
Changelog since v5
o Changelog clarification in patch 1
o Additional comments in patch 2
Changelog since v4
o Avoid pcp->count getting out of sync if struct page gets corrupted
Changelog since v3
o Allow high-order atomic allocations to use reserves
Changelog since v2
o Correct initialisation to avoid -Woverflow warning
The following is two patches that implement a per-cpu cache for high-order allocations, primarily aimed at SLUB. The first patch is a bug fix that is technically unrelated but was discovered by review and so batched together. The second is the patch that implements the high-order pcpu cache.
include/linux/mmzone.h | 20 +++++++- mm/page_alloc.c | 129 ++++++++++++++++++++++++++++++++----------------- 2 files changed, 103 insertions(+), 46 deletions(-)
Signature · 7 lines
2.10.2 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>