From: Rik van Riel <riel@redhat.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Johannes Weiner <hannes@saeurebad.de>,
Peter Zijlstra <peterz@infradead.org>,
Nossum <vegard.nossum@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] mm: more likely reclaim MADV_SEQUENTIAL mappings
Date: Mon, 21 Jul 2008 11:14:12 -0400 [thread overview]
Message-ID: <20080721111412.0bfcd09b@bree.surriel.com> (raw)
In-Reply-To: <200807211549.00770.nickpiggin@yahoo.com.au>
On Mon, 21 Jul 2008 15:49:00 +1000
Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> It is already bad because: if you are doing a big streaming copy
> which you know is going to blow the cache and not be used again,
> then you should be unmapping behind you as you go.
MADV_SEQUENTIAL exists for a reason.
If you think that doing an automatic unmap-behind will be
a better way to go, we can certainly whip up a patch for
that...
--
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>
next prev parent reply other threads:[~2008-07-21 15:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 17:31 Johannes Weiner
2008-07-19 17:59 ` Rik van Riel
2008-07-21 0:09 ` KOSAKI Motohiro
2008-07-21 1:48 ` Andrew Morton
2008-07-21 3:53 ` KOSAKI Motohiro
2008-07-21 5:49 ` Nick Piggin
2008-07-21 15:14 ` Rik van Riel [this message]
2008-07-22 2:02 ` Nick Piggin
2008-07-22 2:36 ` Rik van Riel
2008-07-22 2:54 ` Nick Piggin
2008-07-22 3:04 ` Rik van Riel
2008-07-22 3:43 ` Nick Piggin
2008-07-22 3:49 ` Nick Piggin
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=20080721111412.0bfcd09b@bree.surriel.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@saeurebad.de \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=peterz@infradead.org \
--cc=vegard.nossum@gmail.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