Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

numastat.8: clarify that information relates to resident pages #70

Merged
merged 1 commit into from
Jul 10, 2019

Conversation

stefanha
Copy link

@stefanha stefanha commented Jul 9, 2019

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

Suggested-by: Daniele Palumbo daniele@retaggio.net
Signed-off-by: Stefan Hajnoczi stefanha@redhat.com

@stefanha
Copy link
Author

stefanha commented Jul 9, 2019

The Travis clang 5 & 6 apt-get errors are unrelated to this patch.

@andikleen
Copy link
Contributor

"Virtual memory mappings are not counted" is not accurate. After all the virtual mapping could have (and likely has) memory backing it, then it would be counted.

The first sentence is ok.

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

Suggested-by: Daniele Palumbo <daniele@retaggio.net>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
@stefanha stefanha force-pushed the numastat-man-resident-vs-virtual branch from 1afe8a3 to 56806b0 Compare July 9, 2019 19:46
@stefanha
Copy link
Author

stefanha commented Jul 9, 2019

@andikleen Thanks, I have updated the commit.

@andikleen andikleen merged commit c2b0a95 into numactl:master Jul 10, 2019
@andikleen
Copy link
Contributor

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants