From: "Artem S. Tashkinov" <aros@gmx.com>
To: linux-kernel@vger.kernel.org
Subject: A long standing issue with RAM usage reporting
Date: Wed, 3 Mar 2021 12:30:10 +0000 [thread overview]
Message-ID: <6ea673dc-c34b-ff8f-57f3-bce575b989ce@gmx.com> (raw)
Hello everyone,
I'd love to bring kernel developers' attention to this long standing issue:
https://bugzilla.kernel.org/show_bug.cgi?id=201675
It would be great if something was done about it because otherwise htop,
top and free and numerous other utilities in Linux have to implement
hacks and workarounds to properly report free/used RAM.
https://github.com/htop-dev/htop/issues/556
https://gitlab.com/procps-ng/procps/-/issues/196
There's also another related issue:
https://bugzilla.kernel.org/show_bug.cgi?id=201673 but it will be
automatically solved once the initial bug report has been dealt with.
Best regards,
Artem
reply other threads:[~2021-03-03 17:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6ea673dc-c34b-ff8f-57f3-bce575b989ce@gmx.com \
--to=aros@gmx.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®