From: Rik van Riel <riel@redhat.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] how do we move the VM forward? (was Re: [RFC] cleanup of use-once)
Date: Tue, 3 May 2005 09:16:11 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0505030913480.27756@chimarrao.boston.redhat.com> (raw)
In-Reply-To: <42771904.7020404@yahoo.com.au>
On Tue, 3 May 2005, Nick Piggin wrote:
> I think the biggest problem with our twine and duct tape page reclaim
> scheme is that somehow *works* (for some value of works).
> I think we branch a new tree for all interested VM developers to work
> on and try to get performing well. Probably try to restrict it to page
> reclaim and related fundamentals so it stays as small as possible and
> worth testing.
Sounds great. I'd be willing to maintain a quilt tree for
this - in fact, I've already got a few patches ;)
Also, we should probably keep track of exactly what we're
working towards. I've put my ideas on a wiki page, feel
free to add yours - probably a new page for stuff that's
not page replacement related ;)
http://wiki.linux-mm.org/wiki/AdvancedPageReplacement
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-05-03 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 4:43 [RFC] cleanup of use-once Rik van Riel
2005-05-03 6:24 ` [RFC] how do we move the VM forward? (was Re: [RFC] cleanup of use-once) Nick Piggin
2005-05-03 13:16 ` Rik van Riel [this message]
2005-05-04 0:43 ` Nick Piggin
2005-05-04 0:51 ` [RFC] how do we move the VM forward? (was Re: [RFC] cleanup ofuse-once) David Lang
2005-05-20 18:16 ` Herbert Poetzl
2005-05-20 18:30 ` Lee Revell
2005-05-20 21:24 ` Martin J. Bligh
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=Pine.LNX.4.61.0505030913480.27756@chimarrao.boston.redhat.com \
--to=riel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
/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