Memory reclaim documentation fixes
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | docs: cgroup: Explain reclaim protection targetDocumentation/ | +21 | 0 replies | |
| 2/3 | docs: cgroup: Note about sibling relative reclaim protectionDocumentation/ | +4 | 0 replies | |
| 3/3 | docs: cgroup: No special handling of unpopulated memcgsDocumentation/ | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] Memory reclaim documentation fixes
Hi,
I think the reclaim target is a concept that is not just an implementation detail and hence it should be documented how it applies to protection configuration (the first patch). Second patch is a "best practice" bit of information, it may be squashed with the first one. The last patch just makes docs indefinite until the idea is implemented.
Michal Koutný (3):
docs: cgroup: Explain reclaim protection target
docs: cgroup: Note about sibling relative reclaim protection
docs: cgroup: No special handling of unpopulated memcgs
Documentation/admin-guide/cgroup-v2.rst | 31 ++++++++++++++++++++----- 1 file changed, 25 insertions(+), 6 deletions(-)
Signature · 1 line
2.27.0