From: Dave Chinner <david@fromorbit.com>
To: Elrond <elrond+xfs.oss.sgi.com@samba-tng.org>, xfs@oss.sgi.com
Subject: Re: xfsaild wakeups
Date: Wed, 31 Dec 2008 10:35:22 +1100 [thread overview]
Message-ID: <20081230233522.GB10725@disturbed> (raw)
In-Reply-To: <20081229232915.GA6724@memak.tu-darmstadt.de>
On Tue, Dec 30, 2008 at 12:29:15AM +0100, Elrond wrote:
>
> Hi,
>
> The major issue of xfsaild wakeups was analyzed in
> February. (see
> http://oss.sgi.com/archives/xfs/2008-02/msg00169.html ).
>
> A small issue persists. We're now at 1 wakeup per second
> and mounted filesystem. I have three xfs on my box and the
> number wants to grow. xfsaild is on place two of my
> powertop wakeup list. Sometimes place one.
>
> Is anyone working on reducing this to zero for an idle fs?
It's on the list of things to do given that 2.6.29 will have
the fix for the bug that the periodic wakeup is catching.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2008-12-30 23:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 23:29 xfsaild wakeups Elrond
2008-12-30 23:35 ` Dave Chinner [this message]
2008-12-31 15:30 ` Elrond
2009-01-01 23:54 ` Dave Chinner
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=20081230233522.GB10725@disturbed \
--to=david@fromorbit.com \
--cc=elrond+xfs.oss.sgi.com@samba-tng.org \
--cc=xfs@oss.sgi.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