From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Joe <joeja@mindspring.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Xeon processors &&Hyper-Threading
Date: Fri, 13 Jun 2003 12:39:37 -0400 [thread overview]
Message-ID: <3EE9FE49.2090905@nortelnetworks.com> (raw)
In-Reply-To: 3EE9FDFA.6020803@mindspring.com
Joe wrote:
> 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?
The kernel has full support for hyperthreading. Be aware however that it
doesn't always buy you any performance gain and can actually result in
performance decrease.
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2003-06-13 16:25 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 [this message]
2003-06-13 16:45 ` Richard B. Johnson
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=3EE9FE49.2090905@nortelnetworks.com \
--to=cfriesen@nortelnetworks.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).