From: Andrew Morton <akpm@linux-foundation.org>
To: benh@kernel.crashing.org
Cc: "Robin H. Johnson" <robbat2@gentoo.org>,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>
Subject: Re: Idle loadavg of ~1, maybe MD related
Date: Sat, 5 Jan 2008 19:05:06 -0800 [thread overview]
Message-ID: <20080105190506.38dcf45e.akpm@linux-foundation.org> (raw)
In-Reply-To: <1199528332.7291.53.camel@pasglop>
On Sat, 05 Jan 2008 21:18:52 +1100 Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> On Sat, 2008-01-05 at 02:04 -0800, Robin H. Johnson wrote:
> > On Sat, Jan 05, 2008 at 01:30:37AM -0800, Andrew Morton wrote:
> > > >From that I'd suspect that kwindfarm is being a bad citizen.
> > > If a process is consistently stuck in D state, run
> > Windfarm.
>
> It's an unfortunate artifact that kernel threads that do
> non-interruptible sleep are counted as load...
>
> In the case of windfarm, it does a lot (a _LOT_) of accesses to various
> i2c busses and the SMU (the system management unit which controls the
> fans). All those are done in the form of short requests during which the
> process is doing a wait_for_completion() or similar.
>
> I don't see a better way to do that, I think we could have good use of
> something that stops counting those in the load average...
Maybe, but we can usually work around it pretty comfortably.
If smu_set_fan() is only ever called by a kernel thread then we can simply
flip it over to using wait_for_completion_interruptible().
If smu_set_fan() is also called from user processes then things aren't so
easy...
next prev parent reply other threads:[~2008-01-06 3:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-30 10:06 Idle loadavg of ~1, maybe MD related Robin H. Johnson
2008-01-05 9:30 ` Andrew Morton
2008-01-05 10:04 ` Robin H. Johnson
2008-01-05 10:18 ` Benjamin Herrenschmidt
2008-01-06 3:05 ` Andrew Morton [this message]
2008-01-06 3:53 ` Benjamin Herrenschmidt
2008-01-06 11:21 ` Paul Mackerras
2008-01-06 11:29 ` Robin H. Johnson
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=20080105190506.38dcf45e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=robbat2@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox