All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Gardet <guillaume.gardet@free.fr>
To: Frank Agius <ftagius@yahoo.com>
Cc: linux-omap@vger.kernel.org, openSUSE ARM ML <opensuse-arm@opensuse.org>
Subject: Re: Beagleboard xM - Bogomips are very low
Date: Wed, 20 Mar 2013 17:26:48 +0100	[thread overview]
Message-ID: <5149E348.2040101@free.fr> (raw)
In-Reply-To: <5149B028.9010703@yahoo.com>


Le 20/03/2013 13:48, Frank Agius a écrit :
> On 3/19/2013 11:17 AM, Guillaume Gardet wrote:
>> Hi,
>>
>> On a Beagleboard xM rev. B, I noticed that vanilla kernel 3.4.6 have the
>> folowing bogomips for 300MHz and 800 MHz operations: 262.08 and 700.57.
>>
>> With kernel 3.7.10, I have : 175.65 and 467.41 bogompis.
>>
>> Any idea why bogomips are so low now?
>>
>
> I believe this is the reason for the BogoMIPS change:
>
> http://www.spinics.net/lists/arm-kernel/msg221672.html
>
> It looks like BogoMIPS reporting changed because of the delay routine patch introduced in 3.6.  So the change in BogoMIPS is real, but should not be a concern.

Thanks for the pointer. So, it should not affect performances.
I will try to bench it, to be sure there is no hidden problem.

Thanks.


Guillaume


>
> frank agius
>
>> Guillaume
>>
>> -- 
>> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
>

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2013-03-20 16:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19 15:17 Beagleboard xM - Bogomips are very low Guillaume Gardet
2013-03-19 16:09 ` Nishanth Menon
2013-03-20 12:48 ` Frank Agius
2013-03-20 16:26   ` Guillaume Gardet [this message]

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=5149E348.2040101@free.fr \
    --to=guillaume.gardet@free.fr \
    --cc=ftagius@yahoo.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=opensuse-arm@opensuse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.