Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Fuxin Zhang <fxzhang@ict.ac.cn>
To: emblinux@macrohat.com
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: Re:
Date: Sun, 14 Nov 2004 09:32:03 +0800	[thread overview]
Message-ID: <4196B593.40307@ict.ac.cn> (raw)



macrohat wrote:

>Dear linux-mips:
>
>Thanks!
>
>So,Could I think that BCM1250 is not a type of high performance CPU? as in ARM or Power PC ARCH system,Bogomips is almost equal to CPU clock 
>
Intel P4 has 2X Bogomips than the frequency:)

I think we could not conclude just by this: performance of a CPU is a
complex topic,
its architects may think ALU latency is not important enough for them to
implement
full bypass,instead put their energy on other issues.Nowadays, the
memory hierarchy
performance often dominates.

Of course you can benmark it, for general purpose CPU, SPEC CPU2000 may
be a good choice(www.spec.org)
and there are numerous other free benchmarks too.

>frequency.Is there any way to inprove it with software?
>  
>
The compiler may help a bit by scheduling instructions around.

>	
>
>Regards!
>
>======= 2004-11-13 22:01:00 您在来信中写道:=======
>
>  
>
>>macrohat wrote:
>>
>>    
>>
>>>Hello linux-mips:
>>>
>>>I have a question to ask you: why BCM1250 CPU Bogomips is so much lower than CPU clock frequency,such as:
>>>CPU 700MHz - 465.30 Bogomips, CPU 800MHZ - 532.48 BogoMIPS.And i find out that CPU Bogomips is a fixed value regardless L2 cache open or closed,
>>>
>>> 
>>>
>>>      
>>>
>>This indicates the ALU ops of that CPU have more than one cycle latency.
>>To achieve higher frequency,
>>the pipeline is becoming longer...
>>
>>Bogomips calculation is a short loop which fits well in L1 caches, so L2
>>won't affect the performance.
>>
>>    
>>
>>>Enclosed is the log from the console
>>>
>>>Regards!
>>>				
>>>
>>>        macrohat
>>>        emblinux@macrohat.com
>>>          2004-11-13
>>> 
>>>
>>>      
>>>
>
> 
>				 
>        macrohat
>        emblinux@macrohat.com
>          2004-11-13
>
>  
>

             reply	other threads:[~2004-11-14  1:34 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-14  1:32 Fuxin Zhang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-17  9:09 Paulo Miguel Almeida
2024-10-17  9:12 ` Paulo Miguel Almeida
2020-05-06  5:52 Jiaxun Yang
2020-05-06 17:17 ` Nick Desaulniers
2017-11-13 14:55 Re: Amos Kalonzo
2017-11-13 14:55 ` Re: Amos Kalonzo
2017-02-23 15:09 Qin's Yanjun
2017-02-23 15:09 ` RE: Qin's Yanjun
2010-06-11 14:06 Jabir M
2010-06-11 14:32 ` Manuel Lauss
2010-06-11 17:06   ` Re: David Daney
2010-06-11 17:33     ` Re: Kevin D. Kissell
2010-06-11 18:28       ` Re: Manuel Lauss
2006-01-04 12:50 Sathesh Babu Edara
2006-01-04 13:06 ` Kevin D. Kissell
2006-01-09  7:43   ` Sathesh Babu Edara
2006-01-09  7:43     ` RE: Sathesh Babu Edara
2006-01-09  9:00     ` Kevin D. Kissell
2006-01-09  9:00       ` Re: Kevin D. Kissell
2005-04-28 21:30 Raj Palani
2005-04-28 19:15 Bryan Althouse
2005-05-04 13:55 ` Alex Gonzalez
2005-05-04 14:22   ` Bryan Althouse
2005-05-04 14:22     ` RE: Bryan Althouse
2005-05-04 16:42     ` Ralf Baechle
2005-05-05 14:55   ` Re: Ralf Baechle
2005-05-05 15:08     ` Bryan Althouse
2005-05-05 15:08       ` RE: Bryan Althouse
2005-05-05 15:11       ` Ralf Baechle
2005-05-05 15:57     ` Re: Geert Uytterhoeven
2005-05-05 17:13     ` Re: Christoph Hellwig
2004-11-16  6:09 Re: Fuxin Zhang
2004-11-13 14:47 Re: macrohat
2004-09-03  8:57 xuhaoz
2004-09-03 21:47 ` Fuxin Zhang
2004-08-27  1:49 Re: bel racu
2004-04-14  6:05 caoxiang
2004-04-14 18:34 ` Fuxin Zhang
2003-11-01  1:38 Lyle Bainbridge
2003-11-03 18:14 ` Pete Popov

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=4196B593.40307@ict.ac.cn \
    --to=fxzhang@ict.ac.cn \
    --cc=emblinux@macrohat.com \
    --cc=linux-mips@linux-mips.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