linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fengguang Wu <wfg@mail.ustc.edu.cn>
To: Andrew Morton <akpm@osdl.org>
Cc: Ken Chen <kenchen@google.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/4] [RFC][PATCH] fs-writeback: redefining the dirty inode queues
Date: Fri, 10 Aug 2007 14:34:12 +0800	[thread overview]
Message-ID: <386727659.27809@ustc.edu.cn> (raw)
Message-ID: <20070810063412.238042387@mail.ustc.edu.cn> (raw)

Andrew,

I'd like to propose a cleaner way of using the s_dirty, s_io, s_more_io
queues for the writeback of dirty inodes. The basic idea is to clearly
define the function of the queues, especially to decouple s_diry from
s_io/s_more_io.  The details are in the changelog of patch 2.

The patches are some cleanups on top of Andrew's s_dirty time-ordering
patches and Ken's s_more_io patch:

[PATCH 1/4] writeback: check time-ordering of s_io and s_more_io
[PATCH 2/4] writeback: 3-queue based writeback schedule
[PATCH 3/4] writeback: function renames and cleanups
[PATCH 4/4] writeback: fix ntfs with sb_has_dirty_inodes()

 fs/fs-writeback.c  |  196 +++++++++++++++++++++++--------------------
 fs/ntfs/super.c    |    4 
 include/linux/fs.h |    1 
 3 files changed, 108 insertions(+), 93 deletions(-)

Note that the patches need rework for inserting into the right place of
your queue of -mm patches. I'll take care of it in the next take.

Thank you,
Fengguang
-- 

             reply	other threads:[~2007-08-10  6:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070810063412.238042387@mail.ustc.edu.cn>
2007-08-10  6:34 ` Fengguang Wu [this message]
2007-08-10  6:34 ` [PATCH 0/4] [RFC][PATCH] fs-writeback: redefining the dirty inode queues Fengguang Wu
     [not found] ` <20070810063419.454829766@mail.ustc.edu.cn>
2007-08-10  6:34   ` [PATCH 1/4] writeback: check time-ordering of s_io and s_more_io Fengguang Wu
2007-08-10  6:34   ` Fengguang Wu
     [not found] ` <20070810063419.549052142@mail.ustc.edu.cn>
2007-08-10  6:34   ` [PATCH 2/4] writeback: 3-queue based writeback schedule Fengguang Wu
2007-08-10  6:34   ` Fengguang Wu
     [not found]   ` <20070810164715.GA5508@mail.ustc.edu.cn>
2007-08-10 16:47     ` Fengguang Wu
2007-08-10 16:47     ` Fengguang Wu
     [not found]     ` <20070810170534.GA5137@mail.ustc.edu.cn>
2007-08-10 17:05       ` Fengguang Wu
     [not found] ` <20070810063419.657077419@mail.ustc.edu.cn>
2007-08-10  6:34   ` [PATCH 3/4] writeback: function renames and cleanups Fengguang Wu
2007-08-10  6:34   ` Fengguang Wu
     [not found] ` <20070810063419.786586676@mail.ustc.edu.cn>
2007-08-10  6:34   ` [PATCH 4/4] writeback: fix ntfs with sb_has_dirty_inodes() Fengguang Wu
2007-08-10  6:34   ` Fengguang Wu

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=386727659.27809@ustc.edu.cn \
    --to=wfg@mail.ustc.edu.cn \
    --cc=akpm@osdl.org \
    --cc=kenchen@google.com \
    /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).