From: Peter Zijlstra <peterz@infradead.org>
To: Simon Klinkert <simon.klinkert@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
mingo@redhat.com, Trond.Myklebust@netapp.com
Subject: Re: Meaningless load?
Date: Wed, 10 Oct 2012 18:22:44 +0200 [thread overview]
Message-ID: <1349886164.1279.20.camel@twins> (raw)
In-Reply-To: <98F2F644-D531-42FE-B080-9561142D71C8@gmail.com>
On Wed, 2012-10-10 at 17:44 +0200, Simon Klinkert wrote:
> I'm just wondering if the 'load' is really meaningful in this
> scenario. The machine is the whole time fully responsive and looks
> fine to me but maybe I didn't understand correctly what the load
> should mean. Is there any sensible interpretation of the load?
I'll leave meaningful aside, but uninterruptible (D state) is part of
how the load thing is defined, so your 500 result is correct.
next prev parent reply other threads:[~2012-10-10 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 15:44 Meaningless load? Simon Klinkert
2012-10-10 16:22 ` Peter Zijlstra [this message]
2012-10-11 7:19 ` Simon Klinkert
2012-10-11 8:13 ` Mike Galbraith
2012-10-11 13:17 ` Simon Klinkert
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=1349886164.1279.20.camel@twins \
--to=peterz@infradead.org \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=simon.klinkert@gmail.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