From: Frederic Weisbecker <fweisbec@gmail.com>
To: Jan Blunck <jblunck@suse.de>
Cc: Jan Kara <jack@suse.cz>,
tytso@mit.edu,
Linux-Kernel Mailinglist <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 0/5] ext2: Preparation to remove BKL
Date: Mon, 12 Apr 2010 23:01:29 +0200 [thread overview]
Message-ID: <20100412210127.GE8285@nowhere> (raw)
In-Reply-To: <1271104905-8804-1-git-send-email-jblunck@suse.de>
On Mon, Apr 12, 2010 at 10:41:40PM +0200, Jan Blunck wrote:
> In this series I've collected the patches that prepare ext2 for BKL removal.
> It consist mostly of cleanups and additionally introduces a spinlock to protect
> some of the superblock's fields against concurrent access. I've addressed the
> feedback kindly provided by Ogawa-san by moving the ext2_write_super() out of
> ext2_setup_super().
>
> These patches have been part of the BKL removal series that I have posted in
> November 2009 already. Since this is more than just removing the usage of the
> big lock I repost it separately for inclusion. This series, at least the last
> patch that includes the s_lock, needs to be merged before Frederics bkl-removal
> branch, if he merges the rest of my patches there.
It looks like this is all about .35 material.
This is going to be hard to have a separate tree to pushdown/remove
the bkl in the mount path if it depends on the ext2 tree.
What about putting that with the fs bkl removal tree? Would that conflict
with other changes in the ext2 tree?
Thanks.
next prev parent reply other threads:[~2010-04-12 21:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 20:41 [PATCH 0/5] ext2: Preparation to remove BKL Jan Blunck
2010-04-12 20:41 ` [PATCH 1/5] ext2: Use ext2_clear_super_error() in ext2_sync_fs() Jan Blunck
2010-04-12 20:41 ` [PATCH 2/5] ext2: Set the write time " Jan Blunck
2010-04-12 20:41 ` [PATCH 3/5] ext2: Remove duplicate code from ext2_sync_fs() Jan Blunck
2010-04-12 20:41 ` [PATCH 4/5] ext2: Move ext2_write_super() out of ext2_setup_super() Jan Blunck
2010-04-13 17:53 ` Jan Kara
2010-04-14 7:55 ` Jan Blunck
2010-04-12 20:41 ` [PATCH 5/5] ext2: Add ext2_sb_info s_lock spinlock Jan Blunck
2010-04-13 19:09 ` Jan Kara
2010-04-14 8:19 ` Jan Blunck
2010-04-14 7:10 ` Jaswinder Singh Rajput
2010-04-14 8:00 ` Jan Blunck
2010-04-12 21:01 ` Frederic Weisbecker [this message]
2010-04-13 9:31 ` [PATCH 0/5] ext2: Preparation to remove BKL Arnd Bergmann
2010-04-13 20:12 ` Frederic Weisbecker
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=20100412210127.GE8285@nowhere \
--to=fweisbec@gmail.com \
--cc=arnd@arndb.de \
--cc=jack@suse.cz \
--cc=jblunck@suse.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.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;
as well as URLs for NNTP newsgroup(s).