extend vmalloc support for constrained allocations
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest4 patches 39 repliesIn review 3 of 4 applied
- v14 patches 21 repliesSuperseded
Patches in v2 3 of 4 applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | mm/vmalloc: alloc GFP_NO{FS,IO} for vmallocmm/ | +20 | 2 replies | |
| 2/4 | mm/vmalloc: add support for __GFP_NOFAILmm/ | +17 | 27 replies | Applied |
| 3/4 | mm/vmalloc: be more explicit about supported gfp flags.mm/ | +8 | 2 replies | Applied |
| 4/4 | mm: allow !GFP_KERNEL allocations for kvmallocinclude/ mm/ net/ +5 more | +15 | 3 replies | Applied |
Reviews trailers per patch
All 4 patches have a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Uladzislau Rezki (Sony) | Dave Chinner | Vlastimil Babka |
|---|---|---|---|
| Series | A-b | A-b | |
| 1/4 | R-b | A-b | |
| 2/4 | A-b | ||
| 3/4 | R-b | A-b | |
| 4/4 | R-b R-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 3 reviewers.
Cover letter [PATCH v2 0/4] extend vmalloc support for constrained allocations
Hi,
The previous version has been posted here [1]
I hope I have addressed all the feedback. There were some suggestions for further improvements but I would rather make this smaller as I cannot really invest more time and I believe further changes can be done on top.
This version is a rebase on top of the current Linus tree. Except for the review feedback and conflicting changes in the area there is only one change to filter out __GFP_NOFAIL from the bulk allocator. This is not necessary strictly speaking AFAICS but I found it less confusing because vmalloc has its fallback strategy and the bulk allocator is meant only for the fast path.
Original cover:
Based on a recent discussion with Dave and Neil [2] I have tried to implement NOFS, NOIO, NOFAIL support for the vmalloc to make life of kvmalloc users easier.
A requirement for NOFAIL support for kvmalloc was new to me but this seems to be really needed by the xfs code.
NOFS/NOIO was a known and a long term problem which was hoped to be handled by the scope API. Those scope should have been used at the reclaim recursion boundaries both to document them and also to remove the necessity of NOFS/NOIO constrains for all allocations within that scope. Instead workarounds were developed to wrap a single allocation instead (like ceph_kvmalloc).
First patch implements NOFS/NOIO support for vmalloc. The second one adds NOFAIL support and the third one bundles all together into kvmalloc and drops ceph_kvmalloc which can use kvmalloc directly now.
I hope I haven't missed anything in the vmalloc allocator.
Thanks!
[1] http://lkml.kernel.org/r/[email protected]
[2] http://lkml.kernel.org/r/[email protected]