linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Andrew Theurer" <habanero@us.ibm.com>
To: "James Bourne" <jbourne@mtroyal.ab.ca>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
	<linux-kernel@vger.kernel.org>,
	"Marcelo Tosatti" <marcelo@conectiva.com.br>
Subject: Re: Linux 2.4.19-rc3 (hyperthreading)
Date: Mon, 29 Jul 2002 20:15:39 -0500	[thread overview]
Message-ID: <000f01c23766$a04259d0$2c060e09@beavis> (raw)
In-Reply-To: Pine.LNX.4.44.0207291838160.20963-100000@skuld.mtroyal.ab.ca


> On Mon, 29 Jul 2002, Andrew Theurer wrote:
>
> > On Monday 29 July 2002 4:28 pm, Alan Cox wrote:
> > > Its quite possible the irq routing ought to be smarter, at the moment
> > > I'm not sure of the best approaches.
> >
> > Agreed, we need some sort of irqbalance, and I intend to test with
Ingo's and
> > Andrea's approaches. With that addition, I may even see an improvement
with
> > hyperthreading. But for an rc release, I think it would be prudent to
revert
> > the "new code" for default hyperthreading behavior, and attack the whole
> > problem in 2.4.20 or later release.
>
> Ingo Molnars patches for .17 and .18 worked
> well for us, and did balance the ints load across all the CPUs very well.
>
> You can find the patches I used agains 2.4.18 at
> http://www.hardrock.org/kernel/
>
> BTW, this was on a production box for approximately one month,
> then the box mysteriously crashed.  Due to the fact that our load wasn't
> utilizing the hyperthreading that much I removed acpismp=force from the
> boot string.
>
> The are balanced across the 2 real CPUs.

Thanks for the info.  Did you get any performance results for before and
after?  I did try Ingo's patch a while back, and I experienced about a 8%
drop in performance.  I did not have hyperthreading on, just a simple case
comparing balance to no balance.  The overhead of the ioapic programming was
too high.  Increasing the time between reroutes by 20 got me back to the
same performance as no balancing at all.  I intend to test his patch again,
along with Andrea's next.

-Andrew Theurer


  reply	other threads:[~2002-07-30  1:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-29 19:54 Linux 2.4.19-rc3 (hyperthreading) Andrew Theurer
2002-07-29 21:28 ` Alan Cox
2002-07-29 20:38   ` Andrea Arcangeli
2002-07-29 23:45     ` Andrea Arcangeli
2002-07-29 23:51       ` Rik van Riel
2002-07-30  0:04         ` Andrea Arcangeli
2002-07-30  0:09         ` J.A. Magallon
2002-07-30  0:32           ` Andrea Arcangeli
2002-07-31  3:08           ` Bill Davidsen
2002-07-31 12:43             ` Rik van Riel
2002-07-31 14:16               ` Sam Vilain
2002-08-01 18:29                 ` Ingo Oeser
2002-07-29 20:58   ` Andrew Theurer
2002-07-30  0:37     ` Alan Cox
2002-07-29 23:42       ` Andrew Theurer
2002-07-30  0:56         ` James Bourne
2002-07-30  0:47     ` James Bourne
2002-07-30  1:15       ` Andrew Theurer [this message]
2002-07-30  3:09         ` James Bourne

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='000f01c23766$a04259d0$2c060e09@beavis' \
    --to=habanero@us.ibm.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jbourne@mtroyal.ab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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;
as well as URLs for NNTP newsgroup(s).