public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Hyperthreading and Kernel 2.4
Date: Tue, 05 Apr 2005 22:27:51 -0600	[thread overview]
Message-ID: <42536547.9040806@shaw.ca> (raw)
In-Reply-To: <3PwnE-7fl-15@gated-at.bofh.it>

duncan@devilnews.de wrote:
> Hey,
> 
> I apologize in advance if this is not the right place
> to ask. Feel free to redirect me there :)
> 
> I just wanted to know if the 2.4 kernel is aware of
> hyperthreading the same way the 2.6 kernel ist or if
> the issues posted earlier

I'm not sure if the stock 2.4 kernels ever had good HT support, but the 
patched 2.4.20 kernel in Red Hat 9, for example, seems to handle it 
reasonably well..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2005-04-06  4:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3PwnE-7fl-15@gated-at.bofh.it>
2005-04-06  4:27 ` Robert Hancock [this message]
2005-04-04  9:42 Hyperthreading and Kernel 2.4 duncan

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=42536547.9040806@shaw.ca \
    --to=hancockr@shaw.ca \
    --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