From: Chris Mason <chris.mason@oracle.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Fengguang Wu <wfg@mail.ustc.edu.cn>,
Andrew Morton <akpm@osdl.org>, David Chinner <dgc@sgi.com>,
Michael Rubin <mrubin@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] [RFC][PATCH] clustered writeback
Date: Mon, 27 Aug 2007 08:43:01 -0400 [thread overview]
Message-ID: <20070827084301.73217bde@think.oraclecorp.com> (raw)
In-Reply-To: <20070827050336.6a7e8e16@laptopd505.fenrus.org>
On Mon, 27 Aug 2007 05:03:36 -0700
Arjan van de Ven <arjan@infradead.org> wrote:
> On Mon, 27 Aug 2007 19:21:52 +0800
> >
> > 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 :)
>
> 25 seconds is quite not good already though.... it takes a disk a
> second or two of no activity to go into low power mode, every 25
> seconds means you now have at least a 10% constant power cost....
>
> I don't know the right answer (well other than "make sure inodes
> aren't dirty", which involves fixing apps to not do as much file
> operations, as well as relatime) but just "every 25s is no big deal"
> isn't really the case ;-(
But fixing this isn't the job of this patch....It needs something like
the laptop mode logic where it says ohhhh, the disk is awake, lets send
stuff down.
kupdate hitting on the disk isn't really a new problem, I'd rather
address it with a different patch series.
-chris
next prev parent reply other threads:[~2007-08-27 12:54 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 ` [PATCH 0/3] [RFC][PATCH] clustered writeback Fengguang Wu
2007-08-27 12:03 ` 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 [this message]
[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=20070827084301.73217bde@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrubin@google.com \
--cc=wfg@mail.ustc.edu.cn \
/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