From: Lee Revell <rlrevell@joe-job.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Dave Hansen <haveblue@us.ibm.com>, Josh Aas <josha@sgi.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
steiner@sgi.com
Subject: Re: bkl cleanup in do_sysctl
Date: Tue, 10 Aug 2004 16:10:02 -0400 [thread overview]
Message-ID: <1092168602.920.8.camel@mindpipe> (raw)
In-Reply-To: <411925FA.2000303@namesys.com>
On Tue, 2004-08-10 at 15:46, Hans Reiser wrote:
> Lee Revell wrote:
> >For example reiserfs uses the BKL for all write locking (!), but it
> >probably would not be too hard to fix, because you can just look at
> >another filesystem that has proper locking.
> >
> >
> Wrong. ;-) Balancing makes it way hard. Use reiser4. That has very
> sophisticated locking that pushes the research envelope, if you want to
> read code to learn about locking.....
>
OK, I will give it a try. Are any of the reiser3 latency issues
reported in the voluntary preemption thread addressed in reiser4?
Lee
prev parent reply other threads:[~2004-08-10 20:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 16:58 bkl cleanup in do_sysctl Josh Aas
2004-08-10 17:28 ` Dave Hansen
2004-08-10 18:51 ` Lee Revell
2004-08-10 19:16 ` Roland Dreier
2004-08-10 19:21 ` Lee Revell
2004-08-10 19:46 ` Hans Reiser
2004-08-10 20:10 ` Lee Revell [this message]
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=1092168602.920.8.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=haveblue@us.ibm.com \
--cc=josha@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=steiner@sgi.com \
/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