linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yury Umanets <umka@namesys.com>
To: Chris Mason <mason@suse.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] reiserfs v3 fixes and features
Date: Thu, 08 Apr 2004 10:22:04 +0300	[thread overview]
Message-ID: <1081408913.3030.23.camel@firefly> (raw)
In-Reply-To: <1081344323.30829.534.camel@watt.suse.com>

On Wed, 2004-04-07 at 16:25, Chris Mason wrote:
> On Wed, 2004-04-07 at 09:06, Yury Umanets wrote:
> 
> > That would be nice to have also improved locking in this
> > features-improvements-fixes patch set. Ask Oleg, he had intention to
> > work on and probably has something done already.
> > 
> 
> I'm assuming you mean getting rid of the BKL, which would be really
> nice. 
yes
>  I'd like to get the current patchset stabilized and in the
> kernel, but even moving to a per fs spin lock instead of the bkl would
> be a welcome change.
> 
> -chris

Last time we have discussed this with Oleg, he said, that there are lots
of stuff relying on the fact, that bkl can be acquired many times by the
same process. And simple replacing bkl by per-superblock lock makes life
just horrible ;)

There something like bkl but per-superblock based is needed. Or lots of
code should be changed, which is not good idea.

But anyway, this should be done one day, and if I have free time
(probably vacation) and it will not be done until that time, I'd like to
work on it along with Oleg and you ;)

-- 
umka
-- 
umka


  reply	other threads:[~2004-04-08  7:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-06 18:03 [PATCH] reiserfs v3 fixes and features Chris Mason
2004-04-06 20:14 ` Marc-Christian Petersen
2004-04-06 21:06   ` Chris Mason
2004-04-07  2:00 ` Chris Wright
2004-04-07 13:19   ` Chris Mason
2004-04-07 14:37     ` Hans Reiser
2004-04-07 13:06 ` Yury Umanets
2004-04-07 13:25   ` Chris Mason
2004-04-08  7:22     ` Yury Umanets [this message]
2004-04-09 22:02       ` Oleg Drokin
2004-04-15  0:30 ` Chris Mason
2004-04-15  2:53   ` Hubert Chan
2004-04-15 11:37     ` Chris Mason
2004-04-15 12:12     ` Nikita Danilov
2004-04-16 18:54   ` Chris Mason
2004-04-16 19:47     ` Marc-Christian Petersen
2004-04-16 19:59       ` Chris Mason
2004-04-16 20:06       ` Marc-Christian Petersen
2004-04-16 20:26         ` Chris Mason
2004-04-16 20:39           ` Chris Mason
2004-04-16 20:44             ` Marc-Christian Petersen
2004-04-16 20:41           ` Marc-Christian Petersen

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=1081408913.3030.23.camel@firefly \
    --to=umka@namesys.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.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;
as well as URLs for NNTP newsgroup(s).