Skip to content

Cpuset hardwall flag: Introduction

[email protected] linux-mm lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 5 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2Cpuset hardwall flag: Switch cpusets to use the bulk cgroup_add_files() APIkernel/cpuset.c+68 -812 replies
2/2Cpuset hardwall flag: Add a mem_hardwall flag to cpusetsDocumentation/cpusets.txt kernel/cpuset.c+46 -281 reply

Reviews trailers per patch

All 2 patches have a Reviewed-by or Acked-by.

PatchLi ZefanPaul Jackson
1/2R-b A-b
2/2A-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH 0/2] Cpuset hardwall flag: Introduction

Currently the cpusets mem_exclusive flag is overloaded to mean both "no-overlapping" and "no GFP_KERNEL allocations outside this cpuset".

These patches add a new mem_hardwall flag with just the allocation restriction part of the mem_exclusive semantics, without breaking backwards-compatibility for those who continue to use just mem_exclusive. Additionally, the cgroup control file registration for cpusets is cleaned up to reduce boilerplate.

--

--
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>