From: Andrew Morton <akpm@linux-foundation.org>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: riel@redhat.com, kosaki.motohiro@jp.fujitsu.com, npiggin@suse.de,
linux-mm@kvack.org
Subject: Re: [PATCH -v2] mm: more likely reclaim MADV_SEQUENTIAL mappings
Date: Tue, 11 Nov 2008 16:00:46 -0800 [thread overview]
Message-ID: <20081111160046.3dca031f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081106095513.GA4639@cmpxchg.org>
On Thu, 6 Nov 2008 10:55:13 +0100
Johannes Weiner <hannes@cmpxchg.org> wrote:
> File pages mapped only in sequentially read mappings are perfect
> reclaim canditates.
>
> This patch makes these mappings behave like weak references, their
> pages will be reclaimed unless they have a strong reference from a
> normal mapping as well.
>
> It changes the reclaim and the unmap path where they check if the page
> has been referenced. In both cases, accesses through sequentially
> read mappings will be ignored.
>
> Signed-off-by: Johannes Weiner <hannes@saeurebad.de>
> Signed-off-by: Rik van Riel <riel@redhat.com>
> Acked-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> CC: Nick Piggin <npiggin@suse.de>
> ---
>
> II: add likely()s to mitigate the extra branches a bit as to Nick's
> suggestion
>
> Benchmark results from KOSAKI Motohiro:
>
> http://marc.info/?l=linux-mm&m=122485301925098&w=2
>
> mm/memory.c | 3 ++-
> mm/rmap.c | 13 +++++++++++--
> 2 files changed, 13 insertions(+), 3 deletions(-)
>
> --- a/mm/rmap.c
> +++ b/mm/rmap.c
> @@ -337,8 +337,17 @@ static int page_referenced_one(struct pa
> goto out_unmap;
> }
>
> - if (ptep_clear_flush_young_notify(vma, address, pte))
> - referenced++;
> + if (ptep_clear_flush_young_notify(vma, address, pte)) {
> + /*
> + * Don't treat a reference through a sequentially read
> + * mapping as such. If the page has been used in
> + * another mapping, we will catch it; if this other
> + * mapping is already gone, the unmap path will have
> + * set PG_referenced or activated the page.
> + */
> + if (likely(!VM_SequentialReadHint(vma)))
> + referenced++;
> + }
>
> /* Pretend the page is referenced if the task has the
> swap token and is in the middle of a page fault. */
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -759,7 +759,8 @@ static unsigned long zap_pte_range(struc
> else {
> if (pte_dirty(ptent))
> set_page_dirty(page);
> - if (pte_young(ptent))
> + if (pte_young(ptent) &&
> + likely(!VM_SequentialReadHint(vma)))
> mark_page_accessed(page);
> file_rss--;
> }
Of course, in the majority of cases those applications which are
performing sequential reads will have forgotten to call
madvise(MADV_SEQUENTIAL).
--
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>
prev parent reply other threads:[~2008-11-12 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 9:55 [PATCH -v2] mm: more likely reclaim MADV_SEQUENTIAL mappings Johannes Weiner
2008-11-12 0:00 ` Andrew Morton [this message]
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=20081111160046.3dca031f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--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.