From: Christoph Hellwig <hch@infradead.org>
To: Jan Blunck <jblunck@suse.de>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [RFC 2/3] BKL: remove from ext2
Date: Thu, 1 Oct 2009 14:01:43 -0400 [thread overview]
Message-ID: <20091001180143.GA22497@infradead.org> (raw)
In-Reply-To: <1254324604-20243-3-git-send-email-jblunck@suse.de>
On Wed, Sep 30, 2009 at 05:30:03PM +0200, Jan Blunck wrote:
> Remove the big kernel lock from ext2 and replace it with a per superblock
> mutex.
Might be worth taking a look what the other ext brothers are doing in
that area and doing proper finer-grained locking?
next prev parent reply other threads:[~2009-10-01 18:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 15:30 [RFC 0/3] Remove BKL from fs/ Jan Blunck
2009-09-30 15:30 ` [RFC 1/3] BKL pushdown from do_new_mount() to the filesystems Jan Blunck
2009-09-30 15:46 ` Matthew Wilcox
2009-10-01 18:05 ` Jan Blunck
2009-10-08 15:49 ` Boaz Harrosh
2009-10-31 12:26 ` Jan Blunck
2009-09-30 15:30 ` [RFC 2/3] BKL: remove from ext2 Jan Blunck
2009-10-01 18:01 ` Christoph Hellwig [this message]
2009-10-31 12:24 ` Jan Blunck
2009-10-07 5:44 ` Andi Kleen
2009-09-30 15:30 ` [RFC 3/3] BKL: Remove default_llseek() Jan Blunck
2009-10-01 18:06 ` Christoph Hellwig
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=20091001180143.GA22497@infradead.org \
--to=hch@infradead.org \
--cc=jblunck@suse.de \
--cc=linux-fsdevel@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.