From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
ck list <ck@vds.kolivas.org>,
linux-mm@kvack.org, Paul Jackson <pj@sgi.com>
Subject: Re: [PATCH] mm: Implement Swap Prefetching v22
Date: Fri, 10 Feb 2006 01:21:09 +1100 [thread overview]
Message-ID: <43EB4FD5.20107@yahoo.com.au> (raw)
In-Reply-To: <200602100047.09722.kernel@kolivas.org>
Con Kolivas wrote:
> I really don't want to go throwing out pagecache without some smart semantics
> and then swap in random stuff that could be crap I agree. The answer to this
> is for the vm itself to have an ageing algorithm like the clockpro stuff
> which does this in a smart way. It could certainly age away the updatedb
> wrinkles and leave some free ram - which would help/be helped by prefetching.
>
AFAIK clockpro will not leave free ram, will it?
Getting a little hand-wavy; I don't think the updatedb problem needs to
be fixed by a really fancy page reclaim algorithm (IMO, and that's not to
say that a fancy reclaim algorithm wouldn't be nice for other reasons).
Just small improvements here and there, and there will always be a tradeoff
between throughput and interactive pagein latency so in the end it might
need a tunable (hey there is one - maybe it needs to be improved)
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
--
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:[~2006-02-09 14:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 12:39 Con Kolivas
2006-02-09 13:29 ` Nick Piggin
2006-02-09 13:47 ` Con Kolivas
2006-02-09 14:10 ` Nick Piggin
2006-02-09 14:12 ` Con Kolivas
2006-02-09 14:21 ` Nick Piggin [this message]
2006-02-09 22:48 ` Con Kolivas
2006-02-09 14:51 ` Con Kolivas
2006-02-10 1:04 ` Con Kolivas
2006-02-09 18:04 ` Nikita Danilov
2006-02-10 0:08 ` Con Kolivas
2006-02-09 15:12 ` Paul Jackson
2006-02-09 15:33 ` Con Kolivas
2006-02-10 0:51 ` KAMEZAWA Hiroyuki
2006-02-10 0:56 ` Con Kolivas
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=43EB4FD5.20107@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=ck@vds.kolivas.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pj@sgi.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