linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: w@1wt.eu (Willy Tarreau)
To: linux-arm-kernel@lists.infradead.org
Subject: About the accuracy of delay loop
Date: Wed, 10 Aug 2016 17:20:28 +0200	[thread overview]
Message-ID: <20160810152028.GA7732@1wt.eu> (raw)
In-Reply-To: <20160810225939.7f3142ba@JAMIE.lan>

On Wed, Aug 10, 2016 at 10:59:39PM +0800, Jamie Huang wrote:
> Thank you for reply. But the users may be confused because of the
> different results. You mean there is no need to worry about it? 

The bogomips are already a bogus measure. I've been used to see different
values for kernels running in ARM mode versus Thumb2 mode on the same machine,
likely due to different optimizations. What matters is that the LPJ value is
correct for the executed loop so that udelay calculation is accurate enough.
Here everything's OK.

Willy

  reply	other threads:[~2016-08-10 15:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10  7:24 About the accuracy of delay loop Jamie Huang
2016-08-10  7:34 ` Jisheng Zhang
2016-08-10 14:59   ` Jamie Huang
2016-08-10 15:20     ` Willy Tarreau [this message]
2016-08-10 15:43   ` Russell King - ARM Linux

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=20160810152028.GA7732@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).