From: Khalid Aziz <khalid.aziz@oracle.com>
To: Mikko Rantalainen <mikko.rantalainen@peda.net>,
Matthew Wilcox <willy@infradead.org>,
Vlastimil Babka <vbabka@suse.cz>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Why is Shmem included in Cached in /proc/meminfo?
Date: Mon, 30 Aug 2021 13:38:29 -0600 [thread overview]
Message-ID: <4556646fd511050f41b517173d85888e3bd7cef3.camel@oracle.com> (raw)
In-Reply-To: <0cdd0624-fcc3-386e-c651-7173dc3cbb59@peda.net>
On Mon, 2021-08-30 at 20:26 +0300, Mikko Rantalainen wrote:
> ... deleted ...
> Of course one possible solution is to keep "Cached" as is and
> introduce
> "Cache" with the real cache semantics (that is, it includes sum of
> (Cached - Shmem) and memory backed RAM). That way system
> administrators
> would at least see two different fields with unique values and look
> for
> the documentation.
>
I would recommend adding new field. There is likely to be a good number
of tools/scripts out there that already interpret the data from
/proc/meminfo and possily take actions based upon that data. Those
tools will break if we change the sense of existing data. A new field
has the down side of expanding the output further but it also doesn't
break existing tols.
--
Khalid
next prev parent reply other threads:[~2021-08-30 19:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5a42eb2b-fd7b-6296-f5d6-619661ad1418@peda.net>
2021-08-30 14:34 ` Randy Dunlap
2021-08-30 14:41 ` Matthew Wilcox
2021-08-30 16:05 ` Vlastimil Babka
2021-08-30 16:17 ` Matthew Wilcox
2021-08-30 17:26 ` Mikko Rantalainen
2021-08-30 19:38 ` Khalid Aziz [this message]
2021-09-01 8:57 ` Mikko Rantalainen
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=4556646fd511050f41b517173d85888e3bd7cef3.camel@oracle.com \
--to=khalid.aziz@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mikko.rantalainen@peda.net \
--cc=rdunlap@infradead.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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