From: Christoph Hellwig <hch@caldera.de>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: velco@fadata.bg
Subject: [PATCH] updated radix-tree pagecache
Date: Sun, 24 Mar 2002 12:34:14 +0100 [thread overview]
Message-ID: <20020324123414.A12686@caldera.de> (raw)
I've just uploaded a new version of the radix-tree pagecache patch
to kernel.org. This version should fix the OOPSens in the last
version by beeing more carefull with the page->flags handling.
I have tested the 2.4 version under varying loads for about 20 hours
now and it seems stabel, the 2.5 version just got a compiles & boots,
I don't really trust 2.5 in this stage..
The only real difference between the two patches is the use of Ingo
Molnar's mempool interface in the 2.5 version, this is needed to not
deadlock under extreme loads. If you want to have this with a 2.4-based
kernel you have to get a mempool backport from somewhere and just copy
lib/radix-tree.c from the 2.5 radix pagecache patch.
The patches are located at:
ftp://ftp.kernel.org/pub/linux/kernel/people/hch/patches/v2.4/2.4.19-pre4/linux-2.4.19-radixpagecache.patch.gz
ftp://ftp.kernel.org/pub/linux/kernel/people/hch/patches/v2.4/2.4.19-pre4/linux-2.4.19-radixpagecache.patch.bz2
ftp://ftp.kernel.org/pub/linux/kernel/people/hch/patches/v2.5/2.5.7/linux-2.5.7-radixpagecache.patch.gz
ftp://ftp.kernel.org/pub/linux/kernel/people/hch/patches/v2.5/2.5.7/linux-2.5.7-radixpagecache.patch.bz2
Please give them some beating so I can declare them ready for 2.5 when
Linus is back from vacation..
Christoph
--
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-03-24 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-24 11:34 Christoph Hellwig [this message]
2002-03-26 9:56 ` Andrew Morton
2002-03-26 13:02 ` Hugh Dickins
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=20020324123414.A12686@caldera.de \
--to=hch@caldera.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=velco@fadata.bg \
/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