public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: HT Benchmarks (was: /proc/cpuinfo and hyperthreading)
Date: 17 Dec 2002 12:44:22 -0800	[thread overview]
Message-ID: <ato2b6$v48$1@cesium.transmeta.com> (raw)
In-Reply-To: 200212170614.gBH6ELs15888@Port.imtp.ilyichevsk.odessa.ua

Followup to:  <200212170614.gBH6ELs15888@Port.imtp.ilyichevsk.odessa.ua>
By author:    Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
In newsgroup: linux.dev.kernel
> 
> As to HT, it's definitely a good thing. Multiple CPUs on a chip is
> a logical step. HT in P4 is rather weak, but future processors will
> likely have more advanced cores.
> 

SMT and SMP-on-chip are two very different things.

> I never heard about HT from AMD camp. I'm curious what they do. ;)

Not have insanely long pipelines, so that a single thread can actually
use the processor functional units?

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

  reply	other threads:[~2002-12-17 20:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200212160004.gBG04g130091@hera.kernel.org>
2002-12-16  2:34 ` [XFS] add missing file xfs_iomap.c Anders Gustafsson
2002-12-16  3:58   ` /proc/cpuinfo and hyperthreading Scott Robert Ladd
2002-12-16  4:02     ` Robert Love
2002-12-16  4:13       ` Scott Robert Ladd
2002-12-16  6:28         ` Zwane Mwaikambo
2002-12-16  6:35           ` Zwane Mwaikambo
2002-12-16 13:38             ` Scott Robert Ladd
2002-12-16 13:54               ` Brian Jackson
2002-12-16 14:10                 ` Richard B. Johnson
2002-12-16 14:56                   ` Scott Robert Ladd
2002-12-16 15:11                     ` Måns Rullgård
2002-12-16 15:44                       ` HT Benchmarks (was: /proc/cpuinfo and hyperthreading) Scott Robert Ladd
2002-12-16 22:38                         ` J.A. Magallon
2002-12-16 23:21                           ` Scott Robert Ladd
2002-12-16 23:27                             ` J.A. Magallon
2002-12-17 11:03                               ` Denis Vlasenko
2002-12-17 20:44                                 ` H. Peter Anvin [this message]
2002-12-16 23:50                             ` H. Peter Anvin
2002-12-17 19:27                           ` Bill Davidsen
2002-12-16 15:52                 ` /proc/cpuinfo and hyperthreading Andrew Theurer
2002-12-16 14:08     ` Dave Jones
2002-12-16 14:36       ` Scott Robert Ladd
2002-12-16  4:39   ` [XFS] add missing file xfs_iomap.c Linus Torvalds
     [not found] <1_0212161441436926@cichlid.com>
2002-12-18 17:56 ` HT Benchmarks (was: /proc/cpuinfo and hyperthreading) Andrew Burgess
2002-12-19 22:04   ` J.A. Magallon

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='ato2b6$v48$1@cesium.transmeta.com' \
    --to=hpa@zytor.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