From: Dave Hansen <haveblue@us.ibm.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, Alexander Viro <viro@math.psu.edu>
Subject: Re: [PATCH] remove BKL from ext2_get_block() version 2
Date: Tue, 05 Mar 2002 17:17:54 -0800 [thread overview]
Message-ID: <3C856E42.50304@us.ibm.com> (raw)
In-Reply-To: <E16iPdM-0004x1-00@the-village.bc.nu>
Alan Cox wrote:
> I certainly am not interested in it. 2.4 locking changes for very big boxes
> strike me as a little dangerous.
I think that I may have presented the patch in the wrong way. The
primary reason I'm doing this is BKL removal. The ext2 code just
happened to be one of the worst offenders that I'd run into. I've been
using the 8-way with dbench because it produces a the worst-case
scenario I can think of. I also like watching it compile kernels in
just over a minute. :)
This patch was also a backport of an Al Viro 2.5 change, so I consider
it pretty safe. Only time and testing can tell, but I've tested it
about as much as I can.
All of this becomes pretty academic if Al decides that he will backport
the 2.5 changes, which we all want to see.
--
Dave Hansen
haveblue@us.ibm.com
next prev parent reply other threads:[~2002-03-06 1:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 0:23 [PATCH] remove BKL from ext2_get_block() version 2 Dave Hansen
2002-03-06 0:40 ` Alexander Viro
2002-03-06 0:51 ` Dave Hansen
2002-03-06 1:19 ` Andrew Morton
2002-03-06 6:57 ` Dave Hansen
2002-03-06 0:50 ` Alan Cox
2002-03-06 1:17 ` Dave Hansen [this message]
[not found] ` <20020306004432.GC5538@matchmail.com>
2002-03-06 1:20 ` Dave Hansen
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=3C856E42.50304@us.ibm.com \
--to=haveblue@us.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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