public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: art@usfltd.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel-x64-smp-multiprocessor-speed & bogomips problem in /proc/cpuinfo
Date: Mon, 19 Jun 2006 19:51:28 -0400	[thread overview]
Message-ID: <20060619235128.GA22345@redhat.com> (raw)
In-Reply-To: <20060619183134.ow8kexp0jd6o0wck@69.222.0.225>

On Mon, Jun 19, 2006 at 06:31:34PM -0500, art@usfltd.com wrote:
 > kernel-x64-smp-multiprocessor-speed & bogomips problem in /proc/cpuinfo
 > 
 > $cat /proc/cpuinfo
 > processor       : 0
 > vendor_id       : AuthenticAMD
 > cpu family      : 15
 > model           : 43
 > model name      : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
 > stepping        : 1
 > cpu MHz         : 1000.000
 > cache size      : 512 KB
 > physical id     : 0
 > siblings        : 2
 > core id         : 0
 > cpu cores       : 2
 > fpu             : yes
 > fpu_exception   : yes
 > cpuid level     : 1
 > wp              : yes
 > flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge  
 > mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext  
 > fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy
 > bogomips        : 2005.64
 > TLB size        : 1024 4K pages
 > clflush size    : 64
 > cache_alignment : 64
 > address sizes   : 40 bits physical, 48 bits virtual
 > power management: ts fid vid ttp
                        ^^^^^^^

Your cpu can (and is) scaling its speed & voltage to save power.
Bogomips will scale accordingly.

		Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2006-06-19 23:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19 23:31 kernel-x64-smp-multiprocessor-speed & bogomips problem in /proc/cpuinfo art
2006-06-19 23:51 ` Dave Jones [this message]
     [not found] <fa.dmtq+XkP55RoiOTQhW+l7Whdwqk@ifi.uio.no>
2006-06-19 23:53 ` Robert Hancock

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=20060619235128.GA22345@redhat.com \
    --to=davej@redhat.com \
    --cc=art@usfltd.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