From: Peter Zijlstra <peterz@infradead.org>
To: Chris Snook <csnook@redhat.com>
Cc: Tim Pepper <lnxninja@us.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Fengguang Wu <wfg@mail.ustc.edu.cn>, riel <riel@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [RFT][PATCH] mm: drop behind
Date: Fri, 13 Jul 2007 10:12:09 +0200 [thread overview]
Message-ID: <1184314329.20032.70.camel@twins> (raw)
In-Reply-To: <46967EE2.8020803@redhat.com>
On Thu, 2007-07-12 at 15:20 -0400, Chris Snook wrote:
> Then do what we do for FADV_SEQUENTIAL. With that advice, we double the
> readahead window. We're already doing readahead, but we do a lot more
> when we have the advice. NOREUSE should put much greater pressure on
> the vm to drop these pages quickly, or perhaps simply eliminate the
> heuristic evaluation of the access pattern and short-circuit straight to
> dropping the pages.
>
> We should be encouraging application writers to actually use things like
> fadvise when they can tune things more intelligently than kernel
> heuristics can.
I like this, I'll see what I can do.. :-)
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Chris Snook <csnook@redhat.com>
Cc: Tim Pepper <lnxninja@us.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Fengguang Wu <wfg@mail.ustc.edu.cn>, riel <riel@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [RFT][PATCH] mm: drop behind
Date: Fri, 13 Jul 2007 10:12:09 +0200 [thread overview]
Message-ID: <1184314329.20032.70.camel@twins> (raw)
In-Reply-To: <46967EE2.8020803@redhat.com>
On Thu, 2007-07-12 at 15:20 -0400, Chris Snook wrote:
> Then do what we do for FADV_SEQUENTIAL. With that advice, we double the
> readahead window. We're already doing readahead, but we do a lot more
> when we have the advice. NOREUSE should put much greater pressure on
> the vm to drop these pages quickly, or perhaps simply eliminate the
> heuristic evaluation of the access pattern and short-circuit straight to
> dropping the pages.
>
> We should be encouraging application writers to actually use things like
> fadvise when they can tune things more intelligently than kernel
> heuristics can.
I like this, I'll see what I can do.. :-)
--
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:[~2007-07-13 8:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 18:50 [RFT][PATCH] mm: drop behind Peter Zijlstra
2007-07-09 18:50 ` Peter Zijlstra
2007-07-11 22:37 ` Tim Pepper
2007-07-11 22:37 ` Tim Pepper
2007-07-12 7:24 ` Peter Zijlstra
2007-07-12 7:24 ` Peter Zijlstra
2007-07-12 19:20 ` Chris Snook
2007-07-12 19:20 ` Chris Snook
2007-07-13 8:12 ` Peter Zijlstra [this message]
2007-07-13 8:12 ` Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2007-07-10 17:32 Al Boldi
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=1184314329.20032.70.camel@twins \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=csnook@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lnxninja@us.ibm.com \
--cc=riel@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=wfg@mail.ustc.edu.cn \
/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.