From: Jason L Tibbitts III <tibbs@math.uh.edu>
To: xfs@oss.sgi.com
Subject: xfsaild 20 wakeups per second
Date: Thu, 09 Jun 2016 11:43:11 -0500 [thread overview]
Message-ID: <ufaeg86e2jk.fsf@epithumia.math.uh.edu> (raw)
I was tuning the power consumption of my new laptop and noticed that
each xfsaild process is still waking up 20 times per second. I found
http://oss.sgi.com/archives/xfs/2012-03/msg00237.html which I think
indicates that this was a workaround for some other issue and wouldn't
be permanent. Unfortunately that was 4+ years ago. I wasn't able to
locate any other discussion about the topic.
Was it determined that the wakeups were going to have to stay
permanently? Or was the issue just not revisited? And if the former,
is there a way to tune the wakeup frequency in any way?
- J<
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2016-06-09 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 16:43 Jason L Tibbitts III [this message]
2016-06-09 17:18 ` xfsaild 20 wakeups per second Brian Foster
2016-06-09 18:08 ` Jason L Tibbitts III
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=ufaeg86e2jk.fsf@epithumia.math.uh.edu \
--to=tibbs@math.uh.edu \
--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