From: Johannes Weiner <hannes@cmpxchg.org>
To: Rik van Riel <riel@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andres Freund <andres@anarazel.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kernel-team@fb.com
Subject: Re: [PATCH 2/3] mm: filemap: only do access activations on reads
Date: Tue, 5 Apr 2016 13:50:59 -0400 [thread overview]
Message-ID: <20160405175059.GA16935@cmpxchg.org> (raw)
In-Reply-To: <1459805987.6219.32.camel@redhat.com>
On Mon, Apr 04, 2016 at 05:39:47PM -0400, Rik van Riel wrote:
> As for hinting, I suspect it may make sense to differentiate
> between whole page and partial page writes, where partial
> page writes use FGP_ACCESSED, and whole page writes do not,
> under the assumption that if we write a partial page, there
> may be a higher chance that other parts of the page get
> accessed again for other writes (or reads).
The writeback cache should handle at least the multiple subpage writes
case.
What I find a little weird about counting accesses from partial writes
only is when a write covers a full page and then parts of the next. We
would cache only a small piece of what's likely one coherent chunk.
Or when a user writes out several pages in a loop of subpage chunks.
This will get even worse to program against when we start having page
cache transparently backed by pages of different sizes.
Because of that I think it'd be better to apply LRU aging decisions
based on type of access rather based on specific request sizes.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Weiner <hannes@cmpxchg.org>
To: Rik van Riel <riel@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andres Freund <andres@anarazel.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kernel-team@fb.com
Subject: Re: [PATCH 2/3] mm: filemap: only do access activations on reads
Date: Tue, 5 Apr 2016 13:50:59 -0400 [thread overview]
Message-ID: <20160405175059.GA16935@cmpxchg.org> (raw)
In-Reply-To: <1459805987.6219.32.camel@redhat.com>
On Mon, Apr 04, 2016 at 05:39:47PM -0400, Rik van Riel wrote:
> As for hinting, I suspect it may make sense to differentiate
> between whole page and partial page writes, where partial
> page writes use FGP_ACCESSED, and whole page writes do not,
> under the assumption that if we write a partial page, there
> may be a higher chance that other parts of the page get
> accessed again for other writes (or reads).
The writeback cache should handle at least the multiple subpage writes
case.
What I find a little weird about counting accesses from partial writes
only is when a write covers a full page and then parts of the next. We
would cache only a small piece of what's likely one coherent chunk.
Or when a user writes out several pages in a loop of subpage chunks.
This will get even worse to program against when we start having page
cache transparently backed by pages of different sizes.
Because of that I think it'd be better to apply LRU aging decisions
based on type of access rather based on specific request sizes.
next prev parent reply other threads:[~2016-04-05 17:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 17:13 [PATCH 0/3] mm: support bigger cache workingsets and protect against writes Johannes Weiner
2016-04-04 17:13 ` Johannes Weiner
2016-04-04 17:13 ` [PATCH 1/3] mm: workingset: only do workingset activations on reads Johannes Weiner
2016-04-04 17:13 ` Johannes Weiner
2016-04-04 17:13 ` [PATCH 2/3] mm: filemap: only do access " Johannes Weiner
2016-04-04 17:13 ` Johannes Weiner
2016-04-04 21:22 ` Andrew Morton
2016-04-04 21:22 ` Andrew Morton
2016-04-04 21:39 ` Rik van Riel
2016-04-04 21:55 ` Andrew Morton
2016-04-04 21:55 ` Andrew Morton
2016-04-05 17:50 ` Johannes Weiner [this message]
2016-04-05 17:50 ` Johannes Weiner
2016-04-04 22:47 ` Johannes Weiner
2016-04-04 22:47 ` Johannes Weiner
2016-04-04 17:13 ` [PATCH 3/3] mm: vmscan: reduce size of inactive file list Johannes Weiner
2016-04-04 17:13 ` Johannes Weiner
2016-04-04 18:52 ` [PATCH 0/3] mm: support bigger cache workingsets and protect against writes Andres Freund
2016-04-04 18:52 ` Andres Freund
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=20160405175059.GA16935@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=andres@anarazel.de \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.