From: Linda Walsh <lkml@tlinx.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfsaild centisecs /proc wakeup control?
Date: Wed, 08 Oct 2008 17:15:32 -0700 [thread overview]
Message-ID: <48ED4D24.8020208@tlinx.org> (raw)
In-Reply-To: <48ED1BD8.60309@sandeen.net>
Eric Sandeen wrote:
> On what kernel?
2.6.26.0 (haven't rebooted to 2.6.26.5 yet)
> As far as the wakeups go, I thought this was fixed; see for example:
> TAKE 977545 - xfsaild causing too many wakeups
---
It may be fixed in a newer kernel...(referring to David's later comment)..
Just looked at it with powertop 1.10:
Wakeups-from-idle per second : 7.1 interval: 10.0s
Top causes for wakeups:
42.9% ( 6.0) xfsaild : schedule_timeout (process_timeout)
14.3% ( 2.0) <kernel core> : clocksource_register (clocksource_watchdog)
8.6% ( 1.2) xfsbufd : schedule_timeout (process_timeout)
7.1% ( 1.0) ip : tg3_open (tg3_timer)
next prev parent reply other threads:[~2008-10-09 0:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 19:44 xfsaild centisecs /proc wakeup control? Linda A. Walsh
2008-10-08 20:45 ` Eric Sandeen
2008-10-09 0:15 ` Linda Walsh [this message]
2008-10-08 20:58 ` 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=48ED4D24.8020208@tlinx.org \
--to=lkml@tlinx.org \
--cc=sandeen@sandeen.net \
--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