From: Eric Sandeen <sandeen@sandeen.net>
To: Linda Walsh <xfs@tlinx.org>
Cc: Linux-Xfs <linux-xfs@oss.sgi.com>
Subject: Re: minor CPU wake-up question
Date: Sat, 10 Nov 2007 22:47:59 -0600 [thread overview]
Message-ID: <4736897F.4070202@sandeen.net> (raw)
In-Reply-To: <47364104.8020106@tlinx.org>
Linda Walsh wrote:
> I recently ran into "powertop" (fr. lesswatts.org) that shows how often
> interrupts awaken a processor under a tickless kernel.
>
> The display indicates the counts are over a 10 second period.
> Barring any disk activity, why would xfsbufd wake up each copy of itself
> up when there doesn't seem like there would be anything to do.
>
> Is a separate process really needed for each partition (that seems to be
> the case)? I don't know if it is 1 interrupt/bufd or 6 on 1, but
> it is fairly constant with 6 interrupts each period.
> FWIW, dirty_writeback_centiseconds is set to 1500(1499) and makes
> no difference in the count.
>
> It doesn't seem to be a big deal, other than it is at the top of the
> interrupt-chart with usually 60% or more of the ticks. Might be nice
> to not have it on top if it isn't necessary...
I think by default, xfsbufd wakes up each second for each filesystem.
See fs.xfs.xfsbufd_centisecs, default 100, or 1s. I think powertop is
reporting wakeups/second, so it looks you have 6 filesystems mounted?
Honestly if that's your most frequent entry, you're probably doing
pretty well...
-Eric
prev parent reply other threads:[~2007-11-11 4:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 23:38 minor CPU wake-up question Linda Walsh
2007-11-11 4:47 ` Eric Sandeen [this message]
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=4736897F.4070202@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-xfs@oss.sgi.com \
--cc=xfs@tlinx.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.