Fix memcg/memory.high in case kmem accounting is enabled
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 28 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | mm/slab: skip memcg reclaim only if in atomic contextmm/ | +11 | 0 replies | |
| 2/2 | mm/slub: do not bypass memcg reclaim for high-order page allocationmm/ | +11 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] Fix memcg/memory.high in case kmem accounting is enabled
Hi,
Tejun reported that sometimes memcg/memory.high threshold seems to be silently ignored if kmem accounting is enabled:
http://www.spinics.net/lists/linux-mm/msg93613.html
It turned out that both SLAB and SLUB try to allocate without __GFP_WAIT first. As a result, if there is enough free pages, memcg reclaim will not get invoked on kmem allocations, which will lead to uncontrollable growth of memory usage no matter what memory.high is set to.
This patch set attempts to fix this issue. For more details please see comments to individual patches.
Thanks,
Vladimir Davydov (2):
mm/slab: skip memcg reclaim only if in atomic context mm/slub: do not bypass memcg reclaim for high-order page allocation
mm/slab.c | 32 +++++++++++--------------------- mm/slub.c | 24 +++++++++++------------- 2 files changed, 22 insertions(+), 34 deletions(-)
Signature · 1 line
2.1.4