https://bugs.kde.org/show_bug.cgi?id=417080
Bug ID: 417080
Summary: Add support for huge pages
Product: ksysguard
Version: 5.16.5
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: ksysguard-b...@kde.org
Reporter: andy...@mail.ru
Target Milestone: ---
Created attachment 125634
--> https://bugs.kde.org/attachment.cgi?id=125634&action=edit
Example of a /proc/<pid>/status file with huge pages
Currently, the Memory column for a process in KSysGuard does not include memory
allocated in anonymous huge pages. There seems to be no way to see how much
RAM, including huge pages, the process is using. Note that Virtual Size does
not work as it includes all mapped address space of the process, not
necessarily the amount of RAM used.
Since huge pages cannot be swapped out to a page file (as of the time of this
writing and to my knowledge), it seems reasonable to include them into the
Memory column value. If not, at least a separate column would be useful.
For an example, I'm attaching /proc/<pid>/status of an ffmpeg process, which
uses huge pages for most of its allocations (through a custom memory
allocator). For this process, KSysGuard shows 64300 K in its Memory column,
while there is actually 1606 MiB more allocated in huge pages.
--
You are receiving this mail because:
You are watching all bug changes.
