From: "David C. Hansen" <haveblue@us.ibm.com>
To: David Lang <david.lang@digitalinsight.com>
Cc: "Robert L. Harris" <Robert.L.Harris@rdlg.net>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Reiser vs EXT3
Date: 31 Oct 2002 14:13:24 -0800 [thread overview]
Message-ID: <1036102404.4272.285.camel@nighthawk> (raw)
In-Reply-To: <Pine.LNX.4.44.0210311248030.25405-100000@dlang.diginsite.com>
On Thu, 2002-10-31 at 12:49, David Lang wrote:
> note that breaking up this locking bottleneckhas been done in the 2.5
> kernel series so when 2.6 is released this should be much less significant
> (Q2 2003 is the current thought, but don't count on it until it's out)
Actually, ext3 has been immune from most of the lock breakups in 2.5.
ext2 used to have a lot of problems with BKL contention resulting from
ext2_get_block() and some other assorted functions. Al Viro cleaned
these up in early 2.5, but ext3 never got the cleanup. It still scales
horribly, even 2.5.45.
--
Dave Hansen
haveblue@us.ibm.com
next prev parent reply other threads:[~2002-10-31 22:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 14:19 Reiser vs EXT3 Robert L. Harris
2002-10-31 19:02 ` David C. Hansen
2002-10-31 20:49 ` David Lang
2002-10-31 21:51 ` Hans Reiser
2002-10-31 22:05 ` Jeff Garzik
2002-10-31 23:03 ` Matthew Kirkwood
2002-10-31 22:10 ` David C. Hansen
2002-10-31 22:13 ` David C. Hansen [this message]
2002-10-31 22:14 ` Hans Reiser
2002-10-31 20:23 ` Samuel Flory
-- strict thread matches above, loose matches on Subject: below --
2002-10-31 22:52 Dieter Nützel
2002-10-31 22:52 ` Dieter Nützel
2002-11-01 1:16 ` David Lang
2002-11-01 0:51 Kevin Brosius
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=1036102404.4272.285.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=Robert.L.Harris@rdlg.net \
--cc=david.lang@digitalinsight.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.