Bug 1730738 - backport numactl manual to clarify the memory usage output
Summary: backport numactl manual to clarify the memory usage output
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: numactl
Version: 8.3
Hardware: All
OS: Linux
Target Milestone: rc
: 8.0
Assignee: Pingfan Liu
QA Contact: qe-baseos-daemons
Jaroslav Klech
Depends On:
Blocks: 1674330
TreeView+ depends on / blocked
Reported: 2019-07-17 13:46 UTC by dbodnarc
Modified: 2020-04-28 17:01 UTC (History)
7 users (show)

Fixed In Version: numactl-2.0.12-9.el8
Doc Type: Enhancement
Doc Text:
.The `numactl` manual entry clarifies the memory usage output With this release of RHEL 8, the manual page for `numactl` explicitly mentions that the memory usage information reflects only the resident pages on the system. The reason for this addition is to eliminate potential confusion for users whether the memory usage information relates to resident pages or virtual memory.
Clone Of:
Last Closed: 2020-04-28 17:01:22 UTC
Type: Feature Request
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github numactl numactl pull 70 0 'None' closed numastat.8: clarify that information relates to resident pages 2021-01-14 02:54:13 UTC
Red Hat Product Errata RHBA-2020:1897 0 None None None 2020-04-28 17:01:57 UTC

Description dbodnarc 2019-07-17 13:46:02 UTC
The man page gives no hint about whether memory usage information
relates to resident pages or virtual memory. The answer may not be
obvious to the user, so explicitly mention that only resident pages are

We would like to backport the following commit:
> https://github.com/numactl/numactl/pull/70

Comment 2 Pingfan Liu 2019-09-16 06:39:42 UTC
Can anybody set the qa_ack+?


Comment 4 Pingfan Liu 2019-12-10 00:58:29 UTC
Can anybody help me to set qa_ack+?


Comment 15 errata-xmlrpc 2020-04-28 17:01:22 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.