9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] hyperthreading
Date: Fri, 26 Dec 2003 19:00:01 -0500	[thread overview]
Message-ID: <e22617b7b2cd8262db779d45e48c9648@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0312261603500.13081-100000@fbsd.cpsc.ucalgary.ca>

On Fri Dec 26 18:06:45 EST 2003, mirtchov@cpsc.ucalgary.ca wrote:
> quick question:
>
> will Plan 9 work with hyperthreading processors? will it recognize them as
> dual-cpus?
>
> can you share experience with those?
>
> thanks: andrey

Depends. In 2002 we bought a dual-processor Xeon machine with
hyperthreading. After enabling the hyperthreading option in the
BIOS setup Plan 9 detects and uses 4 processors. (I don't think
it makes much, if any, improvement to the system's performance).

Earlier this month we tried a new single-processor P4 system
with hyperthreading. Even with the BIOS option set the BIOS MP
table only contains a single processor entry. I haven't bothered
yet to look to see if there's some BIOS problem or if there's
some other way to take advantage of hyperthreading on this
system.


  reply	other threads:[~2003-12-27  0:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-26 23:05 andrey mirtchovski
2003-12-27  0:00 ` jmk [this message]
2003-12-27 18:39   ` jmk
2003-12-28 16:11   ` ron minnich
2003-12-28 22:12     ` Joel Salomon
2003-12-29  1:47       ` William Josephson
2003-12-31 17:08       ` ron minnich
2004-01-05 11:03     ` Vasile Rotaru
2004-01-05 14:31       ` David Presotto
2004-01-05 15:32         ` ron minnich
2003-12-27  4:10 ` [9fans] fossil/venti vdharani
2003-12-27  4:49   ` okamoto
2003-12-27  7:52     ` vdharani
2003-12-27  5:20       ` mirtchov
2003-12-28  4:47       ` okamoto
2003-12-28  8:22         ` vdharani
2003-12-28  6:40           ` andrey mirtchovski

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=e22617b7b2cd8262db779d45e48c9648@plan9.bell-labs.com \
    --to=jmk@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).