public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Cleverdon <jamesclv@us.ibm.com>
To: Mark Watts <m.watts@mrw.demon.co.uk>, linux-kernel@vger.kernel.org
Subject: Re: Xeon  processors &&Hyper-Threading
Date: Mon, 16 Jun 2003 14:49:27 -0700	[thread overview]
Message-ID: <200306161449.27121.jamesclv@us.ibm.com> (raw)
In-Reply-To: <200306141450.11804.m.watts@mrw.demon.co.uk>

On Saturday 14 June 2003 06:50 am, Mark Watts wrote:
> > 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.
>
> I discovered that you need the 'CPU Enumeration' part of ACPI to be enabled
> otherwise the kernel only sees physical processors, not sibling HT
> processors - shouldnt this be selected automatically when you select SMP ?
> -

Not if you have enabled full ACPI, or if you don't have any P4s.  Some folks 
don't want any ACPI in their kernel at all.   8^)

It's possible for 'CPU Enumeration Only' to be turned on auto-magically, but 
no one has written comprehensive enough logic into the config code, yet....

-- 
James Cleverdon
IBM xSeries Linux Solutions
{jamesclv(Unix, preferred), cleverdj(Notes)} at us dot ibm dot com


  reply	other threads:[~2003-06-16 21:35 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
2003-06-14 13:50   ` Mark Watts
2003-06-16 21:49     ` James Cleverdon [this message]
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=200306161449.27121.jamesclv@us.ibm.com \
    --to=jamesclv@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.watts@mrw.demon.co.uk \
    /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