From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: Andrew Morton <akpm@osdl.org>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
npiggin@suse.de, Ingo Molnar <mingo@elte.hu>,
Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@osdl.org>,
Con Kolivas <kernel@kolivas.org>
Subject: Re: [PATCH] Fix smpnice high priority task hopping problem
Date: Thu, 16 Feb 2006 18:58:38 -0800 [thread overview]
Message-ID: <20060216185837.C27025@unix-os.sc.intel.com> (raw)
In-Reply-To: <43F53A42.2090909@bigpond.net.au>; from pwil3058@bigpond.net.au on Fri, Feb 17, 2006 at 01:51:46PM +1100
On Fri, Feb 17, 2006 at 01:51:46PM +1100, Peter Williams wrote:
> Peter Williams wrote:
> > There's a rational argument (IMHO) that this patch should be applied
> > even in the absence of the smpnice patches as it prevents
> > active_load_balance() doing unnecessary work. If this isn't good for
> > hypo threading then hypo threading is a special case and needs to handle
> > it as such.
>
> OK. The good news is that (my testing shows that) the "sched: fix
> smpnice abnormal nice anomalies" fixes the imbalance problem and the
> consequent CPU hopping.
Thats because find_busiest_group() is no longer showing the imbalance :)
Anyhow if I get time I will review this patch before I start my vacation.
Otherwise I assume Nick and Ingo will review this closely..
> BUT I still think that this patch (modified if necessary to handle any
> HT special cases) should be applied. On a normal system, it will (as
> I've already said) stop active_load_balance() from doing a lot of
> unnecessary work INCLUDING holding the run queue locks for TWO run
> queues for no good reason.
Please see my earlier response to this..
thanks,
suresh
next prev parent reply other threads:[~2006-02-17 2:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 0:39 [PATCH] Fix smpnice high priority task hopping problem Peter Williams
2006-02-17 1:13 ` Siddha, Suresh B
2006-02-17 2:30 ` Peter Williams
2006-02-17 2:51 ` Peter Williams
2006-02-17 2:58 ` Siddha, Suresh B [this message]
2006-02-17 3:16 ` Peter Williams
2006-02-17 2:54 ` Siddha, Suresh B
2006-02-17 3:14 ` Peter Williams
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=20060216185837.C27025@unix-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=akpm@osdl.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=pwil3058@bigpond.net.au \
--cc=rostedt@goodmis.org \
--cc=torvalds@osdl.org \
/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