From: Chris Snook <csnook@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
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: Thu, 12 Jul 2007 15:20:02 -0400 [thread overview]
Message-ID: <46967EE2.8020803@redhat.com> (raw)
In-Reply-To: <1184225086.20032.45.camel@twins>
Peter Zijlstra wrote:
> Hi Tim,
>
> On Wed, 2007-07-11 at 15:37 -0700, Tim Pepper wrote:
>> On 7/9/07, Peter Zijlstra <peterz@infradead.org> wrote:
>>> Use the read-ahead code to provide hints to page reclaim.
>>>
>>> This patch has the potential to solve the streaming-IO trashes my
>>> desktop problem.
>>>
>>> It tries to aggressively reclaim pages that were loaded in a strong
>>> sequential pattern and have been consumed. Thereby limiting the damage
>>> to the current resident set.
>> Interesting...
>>
>> Would it make sense to tie this into (finally) making
>> POSIX_FADV_NOREUSE something more than a noop?
>
> We talked about that, but the thing is, if we make the functionality
> conditional, nobody will ever use it :-/
>
> So, yes, in a perfect world that would indeed make sense. However since
> nobody ever uses these [fm]advise calls,..
>
> So the big question is, does this functionally hurt any workload? If it
> turns out it does (which I still doubt) then we might hide it behind
> knobs, otherwise I'd like to keep it always on.
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.
-- Chris
--
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-12 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 18:50 Peter Zijlstra
2007-07-11 22:37 ` Tim Pepper
2007-07-12 7:24 ` Peter Zijlstra
2007-07-12 19:20 ` Chris Snook [this message]
2007-07-13 8:12 ` Peter Zijlstra
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=46967EE2.8020803@redhat.com \
--to=csnook@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lnxninja@us.ibm.com \
--cc=peterz@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox