From: Paul Jackson <pj@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [DMESG] cpumask_t in action
Date: Fri, 07 Nov 2003 02:06:28 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106817088009058@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106807117402763@msgid-missing>
> The BogoMIPS is another which I would think could be eliminated unless
> it is significantly different from the boot cpu. Maybe say greater
> than 10% different.
Or just show the min and max:
BogoMIPS for 64 CPUs range from 2241.08 to 2298.56
If someone knows they have 32 CPUs at 1.1 GHz, and 32 CPUs at 1.3 GHz,
they don't need to see 32 of these listed as >10% out of spec.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2003-11-07 2:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 22:22 [DMESG] cpumask_t in action Jesse Barnes
2003-11-05 23:18 ` Chen, Kenneth W
2003-11-06 16:51 ` Matthew Wilcox
2003-11-06 17:20 ` Jesse Barnes
2003-11-06 17:23 ` Jesse Barnes
2003-11-06 18:56 ` Luck, Tony
2003-11-06 20:11 ` Jes Sorensen
2003-11-06 20:31 ` Robin Holt
2003-11-07 2:06 ` Paul Jackson [this message]
2003-11-07 8:13 ` Sylvain Jeaugey
2003-11-07 17:24 ` Matthew Wilcox
2003-11-10 8:26 ` Jes Sorensen
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=marc-linux-ia64-106817088009058@msgid-missing \
--to=pj@sgi.com \
--cc=linux-ia64@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