public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrew Theurer <habanero@us.ibm.com>,
	linux-kernel@vger.kernel.org,
	Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: Linux 2.4.19-rc3 (hyperthreading)
Date: Mon, 29 Jul 2002 22:38:40 +0200	[thread overview]
Message-ID: <20020729203840.GA1201@dualathlon.random> (raw)
In-Reply-To: <1027978122.4050.22.camel@irongate.swansea.linux.org.uk>

On Mon, Jul 29, 2002 at 10:28:42PM +0100, Alan Cox wrote:
> On Mon, 2002-07-29 at 20:54, Andrew Theurer wrote:
> > I would caution against having hyperthreading on by default in the 2.4.19 
> > release.  I am seeing a significant degrade in network workloads on P4 with 
> > hyperthreading on.  On 2.4.19-pre10, I get 788 Mbps on NetBench, but on 
> > 2.4.19-rc1 (and probably rc3, should know in an hour), I get 690 Mbps.  It is 
> > clearly a hyperthreading/interrupt routing issue.  On this system (4 x P4), 
> 
> Quite possibly. I've just merged the O(1) scheduler load balancing fixes
> for the hyperthreading stuff, rc3 uses the old scheduler so that isnt

btw, please make sure to merge my patch, the original one had several
severe bugs.

> Its quite possible the irq routing ought to be smarter, at the moment
> I'm not sure of the best approaches.

fixing irq routing is even simpler, should be a three liner, I heard
somebody used kernel threads for it, that's certainly not needed
(btw, also for the irq routing I recommend you to merge my modified
version, the original one looked more to make P4 SMP look like a PIII
in /proc/interrupts not really to improve performance, performance
improves only if the irq stops trashing around and if it stops
overwriting the ioapic registers even if there's no routing change
required).

Andrea

  reply	other threads:[~2002-07-29 20:34 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 [this message]
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
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=20020729203840.GA1201@dualathlon.random \
    --to=andrea@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=habanero@us.ibm.com \
    --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