| Summary: | Memory Subsystem Section of Resource Management Guide needs further details | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Greg Cockburn <gergnz> |
| Component: | doc-Resource_Management_Guide | Assignee: | Martin Prpič <mprpic> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ecs-bugs |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0 | Keywords: | Documentation |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-12-07 12:47:05 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
(In reply to comment #0) > Description of problem: > Greg, this bug has been fixed. Fixed version will appear in the next release. Thank you for reporting this issue. > > Also the order these are placed in cgconfig.conf is important (The reverse > order to which you would set them on the command line). This has been fixed in BZ#622462. Said parameters no longer have to be specified in the reverse order. Martin |
Description of problem: Documentation for doc-Resource_Management_Guide does not detail interdependencies and ordering of memory subsystem values. Version-Release number of selected component (if applicable): 1.0 Section 3.7 (sec-memory) Memory Subsystem memory.limit_in_bytes memory.memsw.limit_in_bytes It needs to be noted that memory.memsw.limit_in_bytes can not be set without first setting memory.limit_in_bytes. Also the order these are placed in cgconfig.conf is important (The reverse order to which you would set them on the command line). e.g. Example A: (VALID): memory { memory.limit_in_bytes = 40; } Example B: (VALID): memory { memory.memsw.limit_in_bytes = 40; memory.limit_in_bytes = 40; } Example C (INVALID): memory { memory.memsw.limit_in_bytes = 40; } Example D (INVALID): memory { memory.limit_in_bytes = 40; memory.memsw.limit_in_bytes = 40; } This is reproducible on the command line: Trying to set a value just for memsw.limit_in_bytes # /bin/echo 50 > /cgroup/memory/patrol/memory.memsw.limit_in_bytes /bin/echo: write error: Invalid argument Now correctly setting a value in limit_in_bytes first. # /bin/echo 50 > /cgroup/memory/patrol/memory.limit_in_bytes # /bin/echo 50 > /cgroup/memory/patrol/memory.memsw.limit_in_bytes