linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: Hyperthreading Patch Results
Date: 8 Dec 2003 04:11:15 GMT	[thread overview]
Message-ID: <br0tl3$cas$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 119145131687.20031206041918@webspires.com

In article <119145131687.20031206041918@webspires.com>,
Russell \"Elik\" Rademacher <elik@webspires.com> wrote:
| Hello linux-kernel,
| 
|   Okay folks.  I have installed it on 28 production servers with that patch contributed by William Lee Irwin III including Dell Servers and 2 Compaq servers among other types of hardware with 3ware, MPT SCSI, straight IDE, MylexRaid in the mix.  I have reported no problems with them and they all correctly reported the HyperThreading CPUs.  Previous versions since 2.4.21 have problems reporting the Hyperthreaded Dual Xeons and report it as 2 CPUs instead of 4.
| 
|   So..I recommend this patch being pushed to 2.4.x tree for inclusion.

Marcello has announced a freeze on any new features in 2.4, so unless
this is considered a bug fix it may not get in.

More to the point, unless Ingo's new HT scheduler changes are accepted
at the same time, I'm not sure this is going to help most people. I will
let people discuss that or not as they please, based on reports of HT
performance, there may actually be regression. I have not tries this
with 2.4 yyet, so I can't say.
-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

      reply	other threads:[~2003-12-08  4:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-06 11:19 Hyperthreading Patch Results Russell "Elik" Rademacher
2003-12-08  4:11 ` bill davidsen [this message]

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='br0tl3$cas$1@gatekeeper.tmr.com' \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).