LKML Archive on
help / color / mirror / Atom feed
From: stable-bot for Nikhil Rao <>
	Peter Zijlstra <>,
	Ingo Molnar <>
Subject: [PATCH 09/28] sched: Do not consider SCHED_IDLE tasks to be cache hot
Date: Thu, 10 Feb 2011 10:23:25 +0100	[thread overview]
Message-ID: <> (raw)

Commit: ef8002f6848236de5adc613063ebeabddea8a6fb upstream
Author: Nikhil Rao <>
AuthorDate: Wed Oct 13 12:09:35 2010 -0700

This patch adds a check in task_hot to return if the task has SCHED_IDLE
policy. SCHED_IDLE tasks have very low weight, and when run with regular
workloads, are typically scheduled many milliseconds apart. There is no
need to consider these tasks hot for load balancing.

Signed-off-by: Nikhil Rao <>
Signed-off-by: Peter Zijlstra <>
LKML-Reference: <>
Signed-off-by: Ingo Molnar <>
Signed-off-by: Mike Galbraith <>
Acked-by: Peter Zijlstra <>
 kernel/sched.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/kernel/sched.c b/kernel/sched.c
index 87e3b2b..0a1fb24 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -2014,6 +2014,9 @@ task_hot(struct task_struct *p, u64 now, struct sched_domain *sd)
 	if (p->sched_class != &fair_sched_class)
 		return 0;
+	if (unlikely(p->policy == SCHED_IDLE))
+		return 0;
 	 * Buddy candidates are cache hot:

                 reply	other threads:[~2011-02-10 12:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \
    --subject='Re: [PATCH 09/28] sched: Do not consider SCHED_IDLE tasks to be cache hot' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).