Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
(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