From: Rik van Riel <riel@redhat.com>
To: Johannes Weiner <hannes@cmpxchg.org>, linux-mm@kvack.org
Cc: Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>,
linux-kernel@vger.kernel.org, kernel-team@fb.com
Subject: Re: [RFC PATCH] proc: do not include shmem and driver pages in /proc/meminfo::Cached
Date: Thu, 18 Feb 2016 16:05:07 -0500 [thread overview]
Message-ID: <1455829507.15821.69.camel@redhat.com> (raw)
In-Reply-To: <1455827801-13082-1-git-send-email-hannes@cmpxchg.org>
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
On Thu, 2016-02-18 at 15:36 -0500, Johannes Weiner wrote:
>
> The semantics of Cached including shmem and kernel pages have been
> this way forever, dictated by the single-LRU implementation rather
>
They may have been that way forever,
but they have also been confusing to
users forever, so ...
> than optimal semantics. So it's an uncomfortable proposal to change
> it
> now. But what other way to fix this for existing users? What other
> way
> to make the interface more intuitive for future users? And what could
> break by removing it now? I guess somebody who already subtracts
> Shmem
> from Cached.
>
> What are your thoughts on this?
>
Reviewed-by: Rik van Riel <riel@redhat.com>
--
All rights reversed
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-02-18 21:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 20:36 [RFC PATCH] proc: do not include shmem and driver pages in /proc/meminfo::Cached Johannes Weiner
2016-02-18 21:05 ` Rik van Riel [this message]
2016-02-18 22:57 ` Hugh Dickins
2016-02-19 6:40 ` Konstantin Khlebnikov
2016-02-19 6:57 ` Konstantin Khlebnikov
2016-02-19 21:13 ` Andrew Morton
2016-02-29 0:03 ` Hugh Dickins
2016-02-29 7:03 ` Konstantin Khlebnikov
2016-02-29 0:02 ` Hugh Dickins
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=1455829507.15821.69.camel@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).