All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ted Tso <tytso@mit.edu>
Cc: Linux Kernel Maling List <linux-kernel@vger.kernel.org>,
	Linux FS Maling List <linux-fsdevel@vger.kernel.org>,
	Ext4 Mailing List <linux-ext4@vger.kernel.org>,
	Jan Kara <jack@suse.cz>
Subject: Re: [PATCH v2 0/4] do not use s_dirt in ext4
Date: Fri, 18 May 2012 13:25:37 +0300	[thread overview]
Message-ID: <1337336737.2483.16.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1333367140-28370-1-git-send-email-artem.bityutskiy@linux.intel.com>

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

Hi Ted,

the merge window is about to open and I am getting worried about this
patch-set - I won't have time to fix it if you indicate an issue...

On Mon, 2012-04-02 at 14:45 +0300, Artem Bityutskiy wrote:
> This patch-set makes ext4 independent of the VFS superblock management
> services. Namely, ext4 does not require to register the 'write_super()' VFS
> call-back.
> 
> The reason of this exercises is to get rid of the 'sync_supers()' kernel thread
> which wakes up every 5 seconds (by default) even if all superblocks are clean.
> This is wasteful from power management POW (unnecessary wake-ups).
> 
> Version 1 of this patch-set can be found here:
> https://lkml.org/lkml/2012/3/20/220
> 
> Changes between v1 and v2.
>   * Rake different strategy - instead of pushing 's_dirt' down "as-is" and
>     emulating old behavior, we now just submit the superblock for writing
>     straight away, either via the journal or directly. Thank to Jan Kara
>     for helping with this.
>   * Ted picked some of the patches already, which made this series shorter
>     - thanks!
>   * This time I've tested the changes using xfstests.
>   * Rebased to 3.4-rc1.
> 
> Note: Ted, you merged the "mm: export dirty_writeback_interval", but it looks
> like we won't need this for ext[23]. However, for other file-systems we will
> need this change.
> 
> Thanks,
> Artem.

-- 
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-05-18 10:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02 11:45 [PATCH v2 0/4] do not use s_dirt in ext4 Artem Bityutskiy
2012-04-02 11:45 ` [PATCH v2 1/4] ext4: Remove useless marking of superblock dirty Artem Bityutskiy
2012-04-12  7:20   ` Artem Bityutskiy
2012-04-30  8:37     ` Artem Bityutskiy
2012-06-01 13:53       ` Artem Bityutskiy
2012-06-01 13:55         ` Artem Bityutskiy
2012-06-01 15:16         ` Ted Ts'o
2012-06-01 17:48           ` Artem Bityutskiy
2012-06-21 13:11           ` Artem Bityutskiy
2012-04-02 11:45 ` [PATCH v2 2/4] ext4: Convert last user of ext4_mark_super_dirty() to ext4_handle_dirty_super() Artem Bityutskiy
2012-04-02 11:45 ` Artem Bityutskiy
2012-04-02 11:45 ` [PATCH v2 3/4] ext4: remove unnecessary superblock dirtying Artem Bityutskiy
2012-04-02 21:49   ` Jan Kara
2012-04-02 11:45 ` [PATCH v2 4/4] ext4: weed out ext4_write_super Artem Bityutskiy
2012-04-02 21:50   ` Jan Kara
2012-05-18 10:25 ` Artem Bityutskiy [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=1337336737.2483.16.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.