All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Jan Kara <jack@suse.cz>,
	Linux FS Maling List <linux-fsdevel@vger.kernel.org>,
	Linux Kernel Maling List <linux-kernel@vger.kernel.org>,
	Ext4 Mailing List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCHv7 0/5] ext4: stop using write_supers and s_dirt
Date: Wed, 11 Jul 2012 17:32:21 +0300	[thread overview]
Message-ID: <1342017141.18274.57.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1342014404-14834-1-git-send-email-dedekind1@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 819 bytes --]

On Wed, 2012-07-11 at 16:46 +0300, Artem Bityutskiy wrote:
> This patch-set makes ext4 file-system stop using the VFS '->write_supers()'
> call-back and the '->s_dirt' superblock field because I plan to remove them
> once all users are gone.

Hi Ted, is there any chance for this stuff to hit 3.6?

Basically I have 3 pending file-systems:
1. ext4 (these patches)
2. sysv - trivial, I hope Andrew would pick them.
3. ufs - should be straight-forward to change the same way I changed
hfs. I'll send patches soon. I hope Andrew would pick them as well.

Everything else - either in upstream or in -mm or in sub-system trees.

After this, I can kill sync_supers and have a chance that Linus would
accept the patches at 3.6-rc1, and end up with sync_super-less 3.6.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2012-07-11 14:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11 13:46 [PATCHv7 0/5] ext4: stop using write_supers and s_dirt Artem Bityutskiy
2012-07-11 13:46 ` [PATCHv7 1/5] ext4: Remove useless marking of superblock dirty Artem Bityutskiy
2012-07-11 13:46 ` [PATCHv7 2/5] ext4: Convert last user of ext4_mark_super_dirty() to ext4_handle_dirty_super() Artem Bityutskiy
2012-07-11 13:46 ` [PATCHv7 3/5] ext4: remove unnecessary superblock dirtying Artem Bityutskiy
2012-07-11 13:46 ` [PATCHv7 4/5] ext4: weed out ext4_write_super Artem Bityutskiy
2012-07-11 13:46 ` [PATCHv7 5/5] ext4: remove unnecessary argument Artem Bityutskiy
2012-07-11 14:32 ` Artem Bityutskiy [this message]
2012-07-23  0:02 ` [PATCHv7 0/5] ext4: stop using write_supers and s_dirt Theodore Ts'o

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=1342017141.18274.57.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@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 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.