linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Banai Zoltan <bazooka@emitel.hu>
To: Kelsey Hudson <khudson@compendium.us>
Cc: James Bourne <jbourne@mtroyal.ab.ca>,
	Hugh Dickins <hugh@veritas.com>,
	"Reed, Timothy A" <timothy.a.reed@lmco.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Hyperthreading
Date: Wed, 21 Aug 2002 23:55:03 +0200	[thread overview]
Message-ID: <20020821215503.GC1669@bazooka.saturnus.vein.hu> (raw)
In-Reply-To: <Pine.LNX.4.44.0208211414190.6621-100000@betelgeuse.compendium-tech.com>

On Wed, Aug 21, 2002 at 02:16:11PM -0700, Kelsey Hudson wrote:
> On Wed, 21 Aug 2002, James Bourne wrote:
> 
> > On Wed, 21 Aug 2002, Hugh Dickins wrote:
> > 
> > > You do need CONFIG_SMP and a processor capable of HyperThreading,
> > > i.e. Pentium 4 XEON; but CONFIG_MPENTIUM4 is not necessary for HT,
> > > just appropriate to that processor in other ways.
> > 
> > I was under the impression that the only CPU capable of hyperthreading was
> > the P4 Xeon.  Is this not correct?  I don't know of any other CPUs that
> > have the ht feature.
> 
> This is currently correct, although I believe Intel has plans to release a 
> Hyperthreading-capable version of its desktop P4. 

If this is correct, and there is not destop P4 capable of ht,
then what does mean the ht flag in cpuinfo?

$cat /proc/cpuinfo 
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 1
model name      : Intel(R) Pentium(R) 4 CPU 1.70GHz
stepping        : 2
cpu MHz         : 1694.907
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
bogomips        : 3381.65
                                                         ^^

> 
> > Also, looking at setup.c it's hard to determine if CONFIG_SMP is
> > actually required, but it doesn't look like it...
> 
> Of course it's required. How are you to take advantage of a "second CPU" 
> if your scheduler only works on a uniprocessor machine?
> 
> -- 
>  Kelsey Hudson                                       khudson@compendium.us
>  Software Engineer/UNIX Systems Administrator
>  Compendium Technologies, Inc                               (619) 725-0771
> ---------------------------------------------------------------------------
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Banai Zoltan

  reply	other threads:[~2002-08-21 22:24 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-21 11:32 Hyperthreading Reed, Timothy A
2002-08-21 13:48 ` Hyperthreading James Bourne
2002-08-21 17:33   ` Hyperthreading Hugh Dickins
2002-08-21 19:34     ` Hyperthreading James Bourne
2002-08-21 21:16       ` Hyperthreading Kelsey Hudson
2002-08-21 21:55         ` Banai Zoltan [this message]
2002-08-22  8:05           ` Hyperthreading venom
2002-08-26 19:00           ` Hyperthreading Kelsey Hudson
2002-08-22  8:00         ` Hyperthreading venom
2002-08-23  7:28     ` Hyperthreading Gilad Ben-Yossef
2002-08-23  8:10       ` Hyperthreading Hugh Dickins
2002-08-23  8:27         ` Hyperthreading Alan Cox
2002-08-23  8:12       ` Hyperthreading venom
  -- strict thread matches above, loose matches on Subject: below --
2003-11-25  9:44 hyperthreading Gábor Lénárt
2003-11-25  9:48 ` hyperthreading Emiliano 'AlberT' Gabrielli
2003-11-25 10:05   ` hyperthreading Gábor Lénárt
2003-11-25 10:16     ` hyperthreading Arjan van de Ven
2003-11-25 10:32     ` hyperthreading Måns Rullgård
2003-11-25 10:45       ` hyperthreading Mikael Pettersson
2003-11-29 13:29   ` hyperthreading Bill Davidsen
2003-12-01 10:53     ` hyperthreading Emiliano 'AlberT' Gabrielli
2003-11-25 10:22 ` hyperthreading Karl Pitrich
2002-08-22 12:58 Hyperthreading Nir Soffer
2002-08-22 14:30 ` Hyperthreading Hugh Dickins
2002-08-22  9:15 Hyperthreading Marc Dietrich
2002-08-22 14:06 ` Hyperthreading Hugh Dickins
2002-08-22 14:36   ` Hyperthreading Marc Dietrich
2002-08-21 22:56 Hyperthreading Nakajima, Jun
2002-08-21 23:45 ` Hyperthreading Alan Cox
2002-04-18  1:52 Hyperthreading Holzrichter, Bruce
2002-04-17 20:34 Hyperthreading Holzrichter, Bruce
2002-04-17 22:48 ` Hyperthreading Martin J. Bligh
2002-04-18  1:21   ` Hyperthreading James Bourne
2002-04-17 20:02 SMP P4 APIC/interrupt balancing James Bourne
2002-04-17 21:10 ` Hyperthreading Martin J. Bligh
2002-04-17 20:15   ` Hyperthreading Robert Love
2002-04-17 20:23     ` Hyperthreading Dave Jones
2002-04-17 21:24     ` Hyperthreading Jeff V. Merkey
2002-04-17 20:25   ` Hyperthreading James Bourne
2002-04-17 21:26   ` Hyperthreading Jeff V. Merkey
2002-04-18  0:31     ` Hyperthreading Martin J. Bligh
2002-04-18  4:50       ` Hyperthreading Jeff V. Merkey
2002-04-17 22:12   ` Hyperthreading Alan Cox

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=20020821215503.GC1669@bazooka.saturnus.vein.hu \
    --to=bazooka@emitel.hu \
    --cc=hugh@veritas.com \
    --cc=jbourne@mtroyal.ab.ca \
    --cc=khudson@compendium.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=timothy.a.reed@lmco.com \
    /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).