From: Pavel Machek <pavel@ucw.cz>
To: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
matthltc@us.ibm.com, nigel@tuxonice.net,
akpm@linux-foundation.org, stable@kernel.org, tglx@linutronix.de,
ntl@pobox.com, mingo@elte.hu
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:sched/urgent] sched: do not count frozen tasks toward load
Date: Fri, 10 Apr 2009 11:20:48 +0200 [thread overview]
Message-ID: <20090410092048.GA30093@elf.ucw.cz> (raw)
In-Reply-To: <tip-e3c8ca8336707062f3f7cb1cd7e6b3c753baccdd@git.kernel.org>
On Thu 2009-04-09 05:39:32, Nathan Lynch wrote:
> Commit-ID: e3c8ca8336707062f3f7cb1cd7e6b3c753baccdd
> Gitweb: http://git.kernel.org/tip/e3c8ca8336707062f3f7cb1cd7e6b3c753baccdd
> Author: Nathan Lynch <ntl@pobox.com>
> AuthorDate: Wed, 8 Apr 2009 19:45:12 -0500
> Committer: Ingo Molnar <mingo@elte.hu>
> CommitDate: Thu, 9 Apr 2009 07:37:02 +0200
>
> sched: do not count frozen tasks toward load
>
> Freezing tasks via the cgroup freezer causes the load average to climb
> because the freezer's current implementation puts frozen tasks in
> uninterruptible sleep (D state).
>
> Some applications which perform job-scheduling functions consult the
> load average when making decisions. If a cgroup is frozen, the load
> average does not provide a useful measure of the system's utilization
> to such applications. This is especially inconvenient if the job
> scheduler employs the cgroup freezer as a mechanism for preempting low
> priority jobs. Contrast this with using SIGSTOP for the same purpose:
> the stopped tasks do not count toward system load.
>
> Change task_contributes_to_load() to return false if the task is
> frozen. This results in /proc/loadavg behavior that better meets
> users' expectations.
>
> Signed-off-by: Nathan Lynch <ntl@pobox.com>
> Acked-by: Andrew Morton <akpm@linux-foundation.org>
> Acked-by: Nigel Cunningham <nigel@tuxonice.net>
> Tested-by: Nigel Cunningham <nigel@tuxonice.net>
> Cc: <stable@kernel.org>
> Cc: containers@lists.linux-foundation.org
> Cc: linux-pm@lists.linux-foundation.org
> Cc: Matt Helsley <matthltc@us.ibm.com>
> LKML-Reference: <20090408194512.47a99b95@manatee.lan>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Acked-by: Pavel Machek <pavel@ucw.cz>
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2009-04-10 9:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 0:45 [PATCH/RFC] do not count frozen tasks toward load Nathan Lynch
[not found] ` <20090408194512.47a99b95-qBK8ZvQsWF7hXIiyNabO3w@public.gmane.org>
2009-04-09 0:56 ` Nigel Cunningham
2009-04-09 0:56 ` Nigel Cunningham
2009-04-09 0:57 ` Andrew Morton
2009-04-09 1:21 ` Nigel Cunningham
2009-04-09 0:56 ` Nigel Cunningham
2009-04-09 0:57 ` Andrew Morton
2009-04-09 0:57 ` Andrew Morton
2009-04-09 1:21 ` Nigel Cunningham
2009-04-09 1:21 ` Nigel Cunningham
2009-04-09 4:37 ` [tip:sched/urgent] sched: " Nathan Lynch
2009-04-09 5:39 ` Nathan Lynch
2009-04-10 9:20 ` Pavel Machek [this message]
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=20090410092048.GA30093@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=matthltc@us.ibm.com \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=nigel@tuxonice.net \
--cc=ntl@pobox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.