linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
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,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 0/7] ext2: Preparation to remove BKL (v2)
Date: Wed, 14 Apr 2010 15:50:48 +0200	[thread overview]
Message-ID: <20100414135048.GE3616@quack.suse.cz> (raw)
In-Reply-To: <1271248719-21488-1-git-send-email-jblunck@suse.de>

On Wed 14-04-10 14:38:32, Jan Blunck wrote:
> This is a series of patches in preparation to the removal of the big kernel
> lock from ext2. It consists mostly of cleanup patches to later introduce a
> spinlock to protect some of the superblock's fields against concurrent access.
> With the spinlock in place we don't need to use the big kernel lock anymore.
> 
> This series has been part of the BKL removal patches that I have posted in
> November 2009 already. I've addressed the feedback kindly provided by Ogawa-san
> by moving the ext2_write_super() out of ext2_setup_super().
> 
> Changes since v1:
> - fix typo when setting MS_RDONLY
> - take s_lock when setting EXT2_FEATURE_COMPAT_EXT_ATTR
> - fold ext2_commit_super() into ext2_sync_super()
> - include BKL removal patch
  OK, I've merged all the patches into my for_testing branch. When it
survives some testing, I'll push them to for_next branch to be pushed
for 2.6.35.

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

      parent reply	other threads:[~2010-04-14 13:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14 12:38 [PATCH 0/7] ext2: Preparation to remove BKL (v2) Jan Blunck
2010-04-14 12:38 ` [PATCH 1/7] ext2: Use ext2_clear_super_error() in ext2_sync_fs() Jan Blunck
2010-04-14 12:38 ` [PATCH 2/7] ext2: Set the write time " Jan Blunck
2010-04-14 12:38 ` [PATCH 3/7] ext2: Remove duplicate code from ext2_sync_fs() Jan Blunck
2010-04-14 12:38 ` [PATCH 4/7] ext2: Fold ext2_commit_super() into ext2_sync_super() Jan Blunck
2010-04-14 12:38 ` [PATCH 5/7] ext2: Move ext2_write_super() out of ext2_setup_super() Jan Blunck
2010-04-14 12:38 ` [PATCH 6/7] ext2: Add ext2_sb_info s_lock spinlock Jan Blunck
2010-04-14 12:38 ` [PATCH 7/7] BKL: Remove BKL from ext2 filesystem Jan Blunck
2010-04-14 13:50 ` Jan Kara [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=20100414135048.GE3616@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=arnd@arndb.de \
    --cc=fweisbec@gmail.com \
    --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).