From: Mark Watts <m.watts@eris.qinetiq.com>
To: linux-kernel@vger.kernel.org
Cc: kladit@t-online.de (Klaus Dittrich)
Subject: Re: brought up 4 cpu's
Date: Mon, 17 Jan 2005 16:32:26 +0000 [thread overview]
Message-ID: <200501171632.26443.m.watts@eris.qinetiq.com> (raw)
In-Reply-To: <41EBE54B.1010401@xeon2.local.here>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Mark Watts wrote:
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >>kernel-2.6.11-rc1-bk5 stops booting after the message
> >>"Brought up 4 CPU'S"
> >>
> >>System is Dual-P4.
> >
> >With HyperThreading?
> >
> >- --
> >Mark Watts
> >Senior Systems Engineer
> >QinetiQ Trusted Information Management
> >Trusted Solutions and Services group
> >GPG Public Key ID: 455420ED
> >
> >-----BEGIN PGP SIGNATURE-----
> >Version: GnuPG v1.2.4 (GNU/Linux)
> >
> >iD8DBQFB6+MrBn4EFUVUIO0RAtBrAJ465HkQ8WVNIx2BXoI+RB7tByIEOQCg3cWo
> >z99P6VMPsaBKYiiPPhuIaDw=
> >=f0sH
> >-----END PGP SIGNATURE-----
>
> Yes, 2 XEON/P4.
Thats your answer then. HyperThreading makes one cpu act as two (with a
suitable performance increase for some workloads)
Mark.
- --
Mark Watts
Senior Systems Engineer
QinetiQ Trusted Information Management
Trusted Solutions and Services group
GPG Public Key ID: 455420ED
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFB6+iaBn4EFUVUIO0RAv6UAKCPVfzInuwygs7+MwVoCoTspzk+9wCg3FCu
0HLcxhzoj+R3ByPPZJ2cqH8=
=TQ1B
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-01-17 16:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-17 15:36 Klaus Dittrich
2005-01-17 16:09 ` Mark Watts
2005-01-17 16:18 ` Klaus Dittrich
2005-01-17 16:32 ` Mark Watts [this message]
2005-01-17 16:29 ` Adrian Bunk
2005-01-18 8:59 ` Mark Watts
2005-01-17 16:31 ` Andrew Walrond
2005-01-17 16:36 ` Matan Peled
2005-01-17 17:07 ` Klaus Dittrich
2005-01-18 22:04 ` Roland Dreier
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=200501171632.26443.m.watts@eris.qinetiq.com \
--to=m.watts@eris.qinetiq.com \
--cc=kladit@t-online.de \
--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
all inboxes | Powered by JetHome®