From: Nick Piggin <piggin@cyberone.com.au>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: colpatch@us.ibm.com, Darren Hart <dvhltc@us.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
"Martin J. Bligh" <mbligh@aracnet.com>,
Rick Lindsley <ricklind@us.ibm.com>,
Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [patch] scheduler: rebalance_tick interval update
Date: Tue, 16 Nov 2004 13:27:16 +1100 [thread overview]
Message-ID: <41996584.5080306@cyberone.com.au> (raw)
In-Reply-To: <41996353.1060604@cyberone.com.au>
Nick Piggin wrote:
>
> Another example, in some ticks, a CPU won't see the updated 'jiffies',
> other
> times it will (at least on Altix systems, this can happen).
>
>
Note that if you didn't want to have this rash of balancing attempted after
a CPU wasn't able to run the rebalance for a long time, the solution would
be to keep adding the balance interval until it becomes greater than the
current jiffies.
I actually prefer it to try to make up the lost balances, just from the
perspective of gathering scheduler statistics. I don't suspect it happens
enough to justify adding the extra logic - Darren, are you actually seeing
problems?
next prev parent reply other threads:[~2004-11-16 2:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 22:38 [patch] scheduler: rebalance_tick interval update Darren Hart
2004-11-16 1:17 ` Nick Piggin
2004-11-16 1:53 ` Matthew Dobson
2004-11-16 2:17 ` Nick Piggin
2004-11-16 2:27 ` Nick Piggin [this message]
2004-11-16 3:50 ` Darren Hart
2004-11-16 3:51 ` Darren Hart
2004-11-16 7:00 ` Rick Lindsley
[not found] ` <1100576400.14742.12.camel@farah.beaverton.ibm.com>
[not found] ` <4199957C.1020804@cyberone.com.au>
2004-11-16 15:56 ` Darren Hart
2004-11-18 16:22 ` Darren Hart
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=41996584.5080306@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--cc=colpatch@us.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=mingo@elte.hu \
--cc=ricklind@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox