public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <wfg@mail.ustc.edu.cn>
To: Chris Mason <chris.mason@oracle.com>
Cc: Andrew Morton <akpm@osdl.org>
Cc: David Chinner <dgc@sgi.com>
Cc: Michael Rubin <mrubin@google.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] [RFC][PATCH] clustered writeback
Date: Mon, 27 Aug 2007 19:21:52 +0800	[thread overview]
Message-ID: <388214369.05937@ustc.edu.cn> (raw)
Message-ID: <20070827112152.816663278@mail.ustc.edu.cn> (raw)

Chris,

This is one possible implementation of the clustered writeback idea.
It runs OK on ext3 (compiling, syncing, etc.).

The patch is based on 2.6.23-rc3-mm1 and the writeback patches here:
http://lkml.org/lkml/2007/8/19/10

By default, with many dirty inodes, it works as follows:
- store dirty inodes in a radix tree, indexed by their inode numbers
- sweep the whole inode number space in 25s and do it in 5 times
- each time we walk only 1/5 of the inode number space
- pull all inodes with dirty-age larger than 5s to the io dispatching queue

Because it does the work in small batches of 10 inodes, when the system has
<=10 dirty inodes, its behavior will reduce to:
- do a full sweep *at once* on every 25s
Which means the disk will flicker once every 25s, not bad :)


The implications for the majority users could be:
- medium-to-heavy writes becomes less seeky
- dirty inodes are getting synced earlier(before: 30s; now: 5-30s)
- less panic for the 'atime' mount option (a future work)

Fengguang
-- 

             reply	other threads:[~2007-08-27 11:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070827112152.816663278@mail.ustc.edu.cn>
2007-08-27 11:21 ` Fengguang Wu [this message]
2007-08-27 12:03   ` [PATCH 0/3] [RFC][PATCH] clustered writeback Arjan van de Ven
     [not found]     ` <20070827122738.GA6999@mail.ustc.edu.cn>
2007-08-27 12:27       ` Fengguang Wu
2007-08-27 12:43     ` Chris Mason
     [not found] ` <20070827113249.031094166@mail.ustc.edu.cn>
2007-08-27 11:21   ` [PATCH 1/3] writeback: introduce queue_dirty() Fengguang Wu
     [not found] ` <20070827113249.173435849@mail.ustc.edu.cn>
2007-08-27 11:21   ` [PATCH 2/3] writeback: introduce dirty_volatile_interval Fengguang Wu
     [not found] ` <20070827113249.306814072@mail.ustc.edu.cn>
2007-08-27 11:21   ` [PATCH 3/3] writeback: writeback clustering by inode number 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=388214369.05937@ustc.edu.cn \
    --to=wfg@mail.ustc.edu.cn \
    --cc=akpm@osdl.org \
    --cc=chris.mason@oracle.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