From: Peter Zijlstra <peterz@infradead.org>
To: Eric Rannaud <eric.rannaud@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>,
riel <riel@redhat.com>
Subject: Re: madvise(2) MADV_SEQUENTIAL behavior
Date: Wed, 16 Jul 2008 14:14:55 +0200 [thread overview]
Message-ID: <1216210495.5232.47.camel@twins> (raw)
In-Reply-To: <1216163022.3443.156.camel@zenigma>
On Tue, 2008-07-15 at 23:03 +0000, Eric Rannaud wrote:
> mm/madvise.c and madvise(2) say:
>
> * MADV_SEQUENTIAL - pages in the given range will probably be accessed
> * once, so they can be aggressively read ahead, and
> * can be freed soon after they are accessed.
>
>
> But as the sample program at the end of this post shows, and as I
> understand the code in mm/filemap.c, MADV_SEQUENTIAL will only increase
> the amount of read ahead for the specified page range, but will not
> influence the rate at which the pages just read will be freed from
> memory.
Correct, various attempts have been made to actually implement this, but
non made it through.
My last attempt was:
http://lkml.org/lkml/2007/7/21/219
Rik recently tried something else based on his split-lru series:
http://lkml.org/lkml/2008/7/15/465
--
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>
next parent reply other threads:[~2008-07-16 12:14 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 [this message]
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
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=1216210495.5232.47.camel@twins \
--to=peterz@infradead.org \
--cc=eric.rannaud@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox