From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@osdl.org, Peter Williams <pwil3058@bigpond.net.au>,
linux-kernel@vger.kernel.org,
Nick Piggin <nickpiggin@yahoo.com.au>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Ingo Molnar <mingo@elte.hu>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>
Subject: Re: [PATCH 5/7] Move idle stat calculation into rebalance_tick()
Date: Sat, 28 Oct 2006 10:57:27 -0700 [thread overview]
Message-ID: <20061028105727.A9917@unix-os.sc.intel.com> (raw)
In-Reply-To: <20061028024138.10809.27755.sendpatchset@schroedinger.engr.sgi.com>; from clameter@sgi.com on Fri, Oct 27, 2006 at 07:41:38PM -0700
On Fri, Oct 27, 2006 at 07:41:38PM -0700, Christoph Lameter wrote:
> Index: linux-2.6.19-rc3/kernel/sched.c
> ===================================================================
> --- linux-2.6.19-rc3.orig/kernel/sched.c 2006-10-27 15:43:45.467245352 -0500
> +++ linux-2.6.19-rc3/kernel/sched.c 2006-10-27 15:45:30.794096498 -0500
> @@ -2849,10 +2849,16 @@ static void update_load(struct rq *this_
> * Balancing parameters are set up in arch_init_sched_domains.
> */
> static void
> -rebalance_tick(int this_cpu, struct rq *this_rq, enum idle_type idle)
> +rebalance_tick(int this_cpu, struct rq *this_rq)
> {
> unsigned long interval;
> struct sched_domain *sd;
> + /*
> + * A task is idle if this is the idle queue
> + * and we have no runnable task
> + */
> + enum idle_type idle = (this_rq->idle && !this_rq->nr_running) ?
> + SCHED_IDLE : NOT_IDLE;
this_rq->idle will always be set to idle task. You wanted to check, if
the current task is idle or not, right? Perhaps we can skip that and
just check for nr_running..
comment needs to be fixed and also please mention that in case of SMT nice,
nr_running will determine if the processor is idle or not(rather than
checking for current task is idle)
thanks,
suresh
next prev parent reply other threads:[~2006-10-28 18:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-28 2:41 [PATCH 0/7] sched_domain balancing via tasklet V2 Christoph Lameter
2006-10-28 2:41 ` [PATCH 1/7] Avoid taking rq lock in wake_priority_sleeper Christoph Lameter
2006-10-28 2:41 ` [PATCH 2/7] Disable interrupts for locking in load_balance() Christoph Lameter
2006-10-28 2:41 ` [PATCH 3/7] Extract load calculation from rebalance_tick Christoph Lameter
2006-10-28 2:41 ` [PATCH 4/7] Stagger load balancing in build_sched_domains Christoph Lameter
2006-10-28 2:41 ` [PATCH 5/7] Move idle stat calculation into rebalance_tick() Christoph Lameter
2006-10-28 17:57 ` Siddha, Suresh B [this message]
2006-10-29 1:05 ` Christoph Lameter
2006-10-28 2:41 ` [PATCH 6/7] Use tasklet to call balancing Christoph Lameter
2006-10-28 2:41 ` [PATCH 7/7] Call tasklet less frequently Christoph Lameter
-- strict thread matches above, loose matches on Subject: below --
2006-11-03 20:46 [PATCH 0/7] sched_domain balancing via tasklet V3 Christoph Lameter
2006-11-03 20:47 ` [PATCH 5/7] Move idle stat calculation into rebalance_tick() Christoph Lameter
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=20061028105727.A9917@unix-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pwil3058@bigpond.net.au \
/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