From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: strange performance behaviour with floats
Date: Mon, 24 Feb 2003 02:25:12 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805914@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805910@msgid-missing>
On Sun, 23 Feb 2003 18:16:57 -0800,
David Mosberger <davidm@napali.hpl.hp.com> wrote:
>Let me say this again: you _don't_ want a single-cycle loop. You want
>a 2-cycle loop that gets twice the work done as a 1-cycle loop. That
>is, you'd want to decrement the loop counter by 2, compare it against
>zero, and branch if it's not zero yet, all the while making sure you
>get a 2-cycle loop.
Now I see what you are getting at, sorry for the confusion.
Of course, the fact that udelay() does not use bogomips at all makes
the whole question irrelevant. We now return you to our regularly
scheduled delay loop :)
next prev parent reply other threads:[~2003-02-24 2:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 1:45 [Linux-ia64] Re: strange performance behaviour with floats Keith Owens
2003-02-24 1:50 ` David Mosberger
2003-02-24 2:01 ` Keith Owens
2003-02-24 2:16 ` David Mosberger
2003-02-24 2:25 ` Keith Owens [this message]
2003-02-24 19:12 ` David Mosberger
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-105590709805914@msgid-missing \
--to=kaos@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