From: Andrew Theurer <habanero@us.ibm.com>
To: "Brian Jackson" <brian-kernel-list@mdrx.com>,
"Scott Robert Ladd" <scott@coyotegulch.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: /proc/cpuinfo and hyperthreading
Date: Mon, 16 Dec 2002 09:52:35 -0600 [thread overview]
Message-ID: <200212160952.35078.habanero@us.ibm.com> (raw)
In-Reply-To: <20021216135453.3823.qmail@escalade.vistahp.com>
On Monday 16 December 2002 07:54, Brian Jackson wrote:
> You could always boot once with nosmp and run some benchmarks and then
> reboot (with smp) and run some more benchmarks, and see if there is a
> difference.
Yes, but wouldn't booting a UP kernel be a better comparison? After all, why
incur any possible overhead of an SMP kernel if you don't need to? Some
benchmarks may not show a difference, but some definitely will.
-Andrew Theurer
next prev parent reply other threads:[~2002-12-16 15:48 UTC|newest]
Thread overview: 23+ 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
2002-12-16 23:50 ` H. Peter Anvin
2002-12-17 19:27 ` Bill Davidsen
2002-12-16 15:52 ` Andrew Theurer [this message]
2002-12-16 14:08 ` /proc/cpuinfo and hyperthreading Dave Jones
2002-12-16 14:36 ` Scott Robert Ladd
2002-12-16 4:39 ` [XFS] add missing file xfs_iomap.c Linus Torvalds
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=200212160952.35078.habanero@us.ibm.com \
--to=habanero@us.ibm.com \
--cc=brian-kernel-list@mdrx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scott@coyotegulch.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
all inboxes | Powered by JetHome®