From: Chris Snook <csnook@redhat.com>
To: Rik van Riel <riel@redhat.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Eric Rannaud <eric.rannaud@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: madvise(2) MADV_SEQUENTIAL behavior
Date: Thu, 17 Jul 2008 14:04:30 -0400 [thread overview]
Message-ID: <487F89AE.9070007@redhat.com> (raw)
In-Reply-To: <20080717102148.6bc52e94@cuia.bos.redhat.com>
Rik van Riel wrote:
> On Thu, 17 Jul 2008 16:14:29 +1000
> Nick Piggin <nickpiggin@yahoo.com.au> wrote:
>
>>> It might encourage user space applications to start using
>>> FADV_SEQUENTIAL or FADV_NOREUSE more often (as it would become
>>> worthwhile to do so), and if they do (especially cron jobs), the problem
>>> of the slow desktop in the morning would progressively solve itself.
>> The slow desktop in the morning should not happen even without such a
>> call, because the kernel should not throw out frequently used data (even
>> if it is not quite so recent) in favour of streaming data.
>>
>> OK, I figure it doesn't do such a good job now, which is sad,
>
> Do you have any tests in mind that we could use to decide
> whether the patch I posted Tuesday would do a decent job
> at protecting frequently used data from streaming data?
>
> http://lkml.org/lkml/2008/7/15/465
>
1) start up a memory-hogging Java app
2) run a full-system backup
If it works well, the Java app shouldn't slow down much.
-- Chris
WARNING: multiple messages have this Message-ID (diff)
From: Chris Snook <csnook@redhat.com>
To: Rik van Riel <riel@redhat.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Eric Rannaud <eric.rannaud@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: madvise(2) MADV_SEQUENTIAL behavior
Date: Thu, 17 Jul 2008 14:04:30 -0400 [thread overview]
Message-ID: <487F89AE.9070007@redhat.com> (raw)
In-Reply-To: <20080717102148.6bc52e94@cuia.bos.redhat.com>
Rik van Riel wrote:
> On Thu, 17 Jul 2008 16:14:29 +1000
> Nick Piggin <nickpiggin@yahoo.com.au> wrote:
>
>>> It might encourage user space applications to start using
>>> FADV_SEQUENTIAL or FADV_NOREUSE more often (as it would become
>>> worthwhile to do so), and if they do (especially cron jobs), the problem
>>> of the slow desktop in the morning would progressively solve itself.
>> The slow desktop in the morning should not happen even without such a
>> call, because the kernel should not throw out frequently used data (even
>> if it is not quite so recent) in favour of streaming data.
>>
>> OK, I figure it doesn't do such a good job now, which is sad,
>
> Do you have any tests in mind that we could use to decide
> whether the patch I posted Tuesday would do a decent job
> at protecting frequently used data from streaming data?
>
> http://lkml.org/lkml/2008/7/15/465
>
1) start up a memory-hogging Java app
2) run a full-system backup
If it works well, the Java app shouldn't slow down much.
-- 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:[~2008-07-17 18:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 23:03 madvise(2) MADV_SEQUENTIAL behavior Eric Rannaud
2008-07-16 12:14 ` Peter Zijlstra
2008-07-16 12:14 ` Peter Zijlstra
2008-07-16 14:50 ` Rik van Riel
2008-07-16 14:50 ` Rik van Riel
2008-07-16 21:05 ` Chris Snook
2008-07-16 21:05 ` Chris Snook
2008-07-17 0:01 ` Eric Rannaud
2008-07-17 0:01 ` Eric Rannaud
2008-07-17 6:14 ` Nick Piggin
2008-07-17 6:14 ` Nick Piggin
2008-07-17 14:21 ` Rik van Riel
2008-07-17 14:21 ` Rik van Riel
2008-07-17 18:04 ` Chris Snook [this message]
2008-07-17 18:04 ` Chris Snook
2008-07-17 18:09 ` Peter Zijlstra
2008-07-17 18:09 ` Peter Zijlstra
2008-07-17 14:20 ` Rik van Riel
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=487F89AE.9070007@redhat.com \
--to=csnook@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=eric.rannaud@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=peterz@infradead.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 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.