[Crash-utility] [RFC PATCH v2 0/2] Show memory overcommit data in dump_kmeminfo()
Brad Hubbard
bhubbard at redhat.com
Mon Dec 1 23:18:27 UTC 2014
On 12/02/2014 02:16 AM, Aaron Tomlin wrote:
> The first patch changes dump_kmeminfo() to report overcommit information
> similar to that displayed under the proc/meminfo file. It may be useful to
> indicate memory over commitment abuse, for example with forced vmcores from
> system hangs due to shortage of memory. The intended output is as follows:
>
> crash> kmem -i
> PAGES TOTAL PERCENTAGE
> TOTAL MEM 1965332 7.5 GB ----
> FREE 78080 305 MB 3% of TOTAL MEM
> USED 1887252 7.2 GB 96% of TOTAL MEM
> SHARED 789954 3 GB 40% of TOTAL MEM
> BUFFERS 110606 432.1 MB 5% of TOTAL MEM
> CACHED 1212645 4.6 GB 61% of TOTAL MEM
> SLAB 146563 572.5 MB 7% of TOTAL MEM
>
> TOTAL SWAP 1970175 7.5 GB ----
> SWAP USED 5 20 KB 0% of TOTAL SWAP
> SWAP FREE 1970170 7.5 GB 99% of TOTAL SWAP
>
> COMMIT LIMIT 2952841 11.3 GB ----
> COMMITTED 1150595 4.4 GB 38% of TOTAL LIMIT
>
> The second patch simply removes the mention of dump_zone_page_usage()
> availability from kmem's help page.
>
> Tested under 3.16.4-200.fc20.x86_64 only.
> Though this should work under RHEL5 (2.6.18) and above.
>
> Aaron Tomlin (2):
> kmem: Show memory commitment data in kmem output
> help: Remove mention of dump_zone_page_usage()
>
> help.c | 40 ++++++++---------
> memory.c | 153 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------
> 2 files changed, 155 insertions(+), 38 deletions(-)
>
Nice work man.
Looking forward to using this in the future.
--
Kindest Regards,
Brad Hubbard
Senior Software Maintenance Engineer
Red Hat Global Support Services
Asia Pacific Region
More information about the Crash-utility
mailing list