From: Andrew Morton <akpm@linux-foundation.org>
To: Nathan Lynch <ntl@pobox.com>
Cc: linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org,
linux-pm@lists.linux-foundation.org, Ingo Molnar <mingo@elte.hu>,
Matt Helsley <matthltc@us.ibm.com>
Subject: Re: [PATCH/RFC] do not count frozen tasks toward load
Date: Wed, 8 Apr 2009 17:57:02 -0700 [thread overview]
Message-ID: <20090408175702.8a99c803.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090408194512.47a99b95@manatee.lan>
On Wed, 8 Apr 2009 19:45:12 -0500 Nathan Lynch <ntl@pobox.com> wrote:
> 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>
> ---
> include/linux/sched.h | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index 011db2f..f8af167 100644
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -202,7 +202,8 @@ extern unsigned long long time_sync_thresh;
> #define task_is_stopped_or_traced(task) \
> ((task->state & (__TASK_STOPPED | __TASK_TRACED)) != 0)
> #define task_contributes_to_load(task) \
> - ((task->state & TASK_UNINTERRUPTIBLE) != 0)
> + ((task->state & TASK_UNINTERRUPTIBLE) != 0 && \
> + (task->flags & PF_FROZEN) == 0)
>
> #define __set_task_state(tsk, state_value) \
> do { (tsk)->state = (state_value); } while (0)
Looks OK to me. It should perhaps use !frozen(task), but the includes
are mucked up.
I suppose we should fix this in -stable too.
next prev parent reply other threads:[~2009-04-09 1:01 UTC|newest]
Thread overview: 15+ 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
2009-04-09 0:56 ` Nigel Cunningham
[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:57 ` Andrew Morton
2009-04-09 0:57 ` Andrew Morton [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2009-04-09 0:45 [PATCH/RFC] " Nathan Lynch
2009-04-09 0:45 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=20090408175702.8a99c803.akpm@linux-foundation.org \
--to=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=ntl@pobox.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 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.