mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andrew Theurer <habanero@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: Linux 2.4.19-rc3 (hyperthreading)
Date: 30 Jul 2002 01:37:25 +0100	[thread overview]
Message-ID: <1027989445.4050.28.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <200207291558.47266.habanero@us.ibm.com>

On Mon, 2002-07-29 at 21:58, Andrew Theurer wrote:
> 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.

Because your personal workload is slower ?

Thats overkill to say the least. Learn to use the kernel boot options


  reply	other threads:[~2002-07-29 23:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-29 19:54 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 [this message]
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=1027989445.4050.28.camel@irongate.swansea.linux.org.uk \
    --to=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

all inboxes | Powered by JetHome®