From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Joe <joeja@mindspring.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Xeon processors &&Hyper-Threading
Date: Fri, 13 Jun 2003 12:45:12 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0306131241330.5894@chaos> (raw)
In-Reply-To: <3EE9FDFA.6020803@mindspring.com>
On Fri, 13 Jun 2003, Joe wrote:
> Does Linux support the Xeon (p4) processor and its capabilities?
>
> The company I work for recently ported its application to Linux and one
> of our current HP clients asked this and I figure it would be just a
> recompile the kernel as a P4, but not sure if this would do it.
>
> I'm not asking if Linux can RUN the Xeon processor.
>
> I'm asking if Linux processor takes any advantage of the Hyper-Threading
> built into this processor?
>
> below is a link to more info on this.
>
> http://www.intel.com/design/xeon/prodbref/
>
> Joe
>
You recompile the kernel for SMP as well as P4. If the motherboard
hasn't disabled HT capabilities, you will take full advantage of
the processor under Linux. Whatever "full advantage" means, is
not absolute, but whatever it is, will be used to its fullest.
Basically, if the code is I/O bound, you'll not see any difference.
If the code is compute-intensive, you will.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.
next prev parent reply other threads:[~2003-06-13 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 16:38 Xeon processors &&Hyper-Threading Joe
2003-06-13 16:39 ` Chris Friesen
2003-06-13 16:45 ` Richard B. Johnson [this message]
2003-06-14 13:50 ` Mark Watts
2003-06-16 21:49 ` James Cleverdon
2003-06-14 18:32 ` Joe
2003-06-14 19:08 ` Joe
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=Pine.LNX.4.53.0306131241330.5894@chaos \
--to=root@chaos.analogic.com \
--cc=joeja@mindspring.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).