From: Nathan Lynch <ntl@pobox.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Matt Helsley <matthltc@us.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Rafael Wysocki <rjw@sisk.pl>, Ingo Molnar <mingo@elte.hu>,
Nigel Cunningham <nigel@tuxonice.net>,
stable@kernel.org, containers@lists.linux-foundation.org,
linux-pm@lists.linux-foundation.org
Subject: Re: [patch 2/2] sched: fix nr_uninterruptible accounting of frozen tasks really
Date: Fri, 17 Jul 2009 15:55:34 -0500 [thread overview]
Message-ID: <1247864134.17553.30.camel@localhost.localdomain> (raw)
In-Reply-To: <1247849254.6522.75.camel@laptop>
On Fri, 2009-07-17 at 18:47 +0200, Peter Zijlstra wrote:
> On Fri, 2009-07-17 at 08:22 -0700, Matt Helsley wrote:
>
> > The job scheduler in question does not use FROZEN as a transient state and
> > does not use checkpoint/restart at all since c/r is still a work in progress.
Right, the job scheduler uses the cgroup freezer as a mechanism to
preempt a low priority job for a higher priority job. (It had used
SIGSTOP in the past.) So in this scenario a frozen cgroup may remain in
that state for a while. Load average is consulted as a measure of
system utilization.
> > Even when used for power management it seems wrong to count frozen tasks
> > towards the loadavg since they aren't using CPU time or waiting for IO.
>
> You're abusing it for _WHAT_?
I think Matt was referring to system-wide suspend/resume/hibernate, not
a behavior of the job scheduler, if that's your concern.
next prev parent reply other threads:[~2009-07-17 20:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 12:24 [patch 0/2] fix load average accounting Thomas Gleixner
2009-07-17 12:24 ` [patch 1/2] sched: fix load average accounting vs. cpu hotplug Thomas Gleixner
2009-07-17 12:25 ` [patch 2/2] sched: fix nr_uninterruptible accounting of frozen tasks really Thomas Gleixner
2009-07-17 12:31 ` Peter Zijlstra
2009-07-17 12:48 ` Thomas Gleixner
2009-07-17 22:26 ` Nigel Cunningham
2009-07-17 15:22 ` Matt Helsley
2009-07-17 16:47 ` Peter Zijlstra
2009-07-17 20:55 ` Nathan Lynch [this message]
2009-07-18 12:56 ` Peter Zijlstra
2009-07-18 23:59 ` Nathan Lynch
2009-07-17 15:51 ` Matt Helsley
2009-07-17 15:55 ` Peter Zijlstra
2009-07-17 16:20 ` Matt Helsley
2009-07-17 20:54 ` Nathan Lynch
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=1247864134.17553.30.camel@localhost.localdomain \
--to=ntl@pobox.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=matthltc@us.ibm.com \
--cc=mingo@elte.hu \
--cc=nigel@tuxonice.net \
--cc=peterz@infradead.org \
--cc=rjw@sisk.pl \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
/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