From: Rik van Riel <riel@redhat.com>
To: Chris Snook <csnook@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Eric Rannaud <eric.rannaud@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>
Subject: Re: madvise(2) MADV_SEQUENTIAL behavior
Date: Thu, 17 Jul 2008 10:20:25 -0400 [thread overview]
Message-ID: <20080717102025.6b7f0e40@cuia.bos.redhat.com> (raw)
In-Reply-To: <487E628A.3050207@redhat.com>
On Wed, 16 Jul 2008 17:05:14 -0400
Chris Snook <csnook@redhat.com> wrote:
> > I believe that for mmap MADV_SEQUENTIAL, we will have to do
> > an unmap-behind from the fault path. Not every time, but
> > maybe once per megabyte, unmapping the megabyte behind us.
> >
> > That way the normal page cache policies (use once, etc) can
> > take care of page eviction, which should help if the file
> > is also in use by another process.
>
> Wouldn't it just be easier to not move pages to the active list when
> they're referenced via an MADV_SEQUENTIAL mapping?
You want to check the MADV_SEQUENTIAL hint at pageout time and
discard the referenced bit from the pte?
> If we keep them on the inactive list, they'll be candidates for
> reclaiming
Only if we ignore the referenced bit. Which I guess we can do.
--
All Rights Reversed
--
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-07-17 14:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1216163022.3443.156.camel@zenigma>
2008-07-16 12:14 ` Peter Zijlstra
2008-07-16 14:50 ` Rik van Riel
2008-07-16 21:05 ` Chris Snook
2008-07-17 0:01 ` Eric Rannaud
2008-07-17 6:14 ` Nick Piggin
2008-07-17 14:21 ` Rik van Riel
2008-07-17 18:04 ` Chris Snook
2008-07-17 18:09 ` Peter Zijlstra
2008-07-17 14:20 ` Rik van Riel [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=20080717102025.6b7f0e40@cuia.bos.redhat.com \
--to=riel@redhat.com \
--cc=csnook@redhat.com \
--cc=eric.rannaud@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterz@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