From: Christoph Hellwig <hch@infradead.org>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH][RC] radix-tree pagecache for 2.5
Date: Tue, 9 Apr 2002 10:47:53 +0100 [thread overview]
Message-ID: <20020409104753.A490@infradead.org> (raw)
I think I have a first release candidate of the radix-tree pagecache for
the 2.5 tree. This patch contains the following changes over the last version
- improved OOM handling all over the place (Andrew Morton)
- minor fixes/cleanuos (Andrew Morton, me)
- switch mapping->page_lock to a r/w lock (me)
The patch can be found at:
ftp://ftp.kernel.org/pub/linux/kernel/people/hch/patches/v2.5/2.5.8-pre2/linux-2.5.8-ratcache.patch.gz
ftp://ftp.kernel.org/pub/linux/kernel/people/hch/patches/v2.5/2.5.8-pre2/linux-2.5.8-ratcache.patch.bz2
In addition a BitKeeper tree is available at http://hkernel.bkbits.net.
--
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/
next reply other threads:[~2002-04-09 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 9:47 Christoph Hellwig [this message]
2002-04-10 2:32 ` Andrew Morton
2002-04-10 4:07 ` [patch] Velikov/Hellwig radix-tree pagecache Andrew Morton
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=20020409104753.A490@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.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