From: Rik van Riel <riel@conectiva.com.br>
To: kernelnewbies@nl.linux.org
Cc: linux-mm@kvack.org
Subject: [PATCH *] VM for 2.4.16
Date: Mon, 26 Nov 2001 19:49:22 -0200 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.33L.0111261943370.1491-100000@duckman.distro.conectiva> (raw)
Hi,
here's a patch which forward-ports my VM to 2.4.16,
integrating the good stuff like blkdev-in-pagecache,
rbtree, smoother zone fallback, etc...
My 64 MB test box seems to be pretty happy doing a
'make -j bzImage' over NFS, so I suspect it's quite
stable now. Please give it a beating.
http://www.surriel.com/patches/2.4/2.4.16-vm
I'll look into making my bitkeeper tree available for
general pulling so everybody can see the detailed
changelog of each file, instead of just the comments
in the patches.
cheers,
Rik
--
DMCA, SSSCA, W3C? Who cares? http://thefreeworld.net/
http://www.surriel.com/ http://distro.conectiva.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/
reply other threads:[~2001-11-26 21:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.33L.0111261943370.1491-100000@duckman.distro.conectiva \
--to=riel@conectiva.com.br \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-mm@kvack.org \
/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