public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: Jason L Tibbitts III <tibbs@math.uh.edu>
Cc: xfs@oss.sgi.com
Subject: Re: xfsaild 20 wakeups per second
Date: Thu, 9 Jun 2016 13:18:57 -0400	[thread overview]
Message-ID: <20160609171857.GA9052@laptop.bfoster> (raw)
In-Reply-To: <ufaeg86e2jk.fsf@epithumia.math.uh.edu>

On Thu, Jun 09, 2016 at 11:43:11AM -0500, Jason L Tibbitts III wrote:
> 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?
> 

The short answer is that the wakeups are probably going to be around for
the immediate future. There was some recent discussion on this here (see
the follow up thread to the patch):

  http://oss.sgi.com/pipermail/xfs/2016-April/048526.html

Brian

>  - J<
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2016-06-09 17:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 16:43 xfsaild 20 wakeups per second Jason L Tibbitts III
2016-06-09 17:18 ` Brian Foster [this message]
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=20160609171857.GA9052@laptop.bfoster \
    --to=bfoster@redhat.com \
    --cc=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