From: Christoph Lameter <christoph@lameter.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Timer updates revision 7 (asm sets predicates/various fixes)
Date: Tue, 03 Aug 2004 21:06:26 +0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0408031405310.21526@server.home> (raw)
In-Reply-To: <Pine.LNX.4.58.0407292044500.3633@schroedinger.engr.sgi.com>
On Tue, 3 Aug 2004, David Mosberger wrote:
> >>>>> On Mon, 2 Aug 2004 19:33:56 -0700 (PDT), christoph@lameter.com said:
>
> Christoph> On Mon, 2 Aug 2004, David Mosberger wrote:
> >> >>>>> On Fri, 30 Jul 2004 08:30:19 -0700 (PDT), Christoph Lameter <clameter@sgi.com> said:
> >>
> Christoph> On Thu, 29 Jul 2004, David Mosberger wrote:
> >> >> It occurred to me now why your numbers are higher: I linked my
> >> >> program statically, whereas yours is probably linked dynamically?
> >>
> Christoph> Correct. But why would this have an influence?
> >>
> >> I'm just trying to determine why our numbers were different. I dont like
> >> unexplained differences.
>
> Christoph> The different numbers may be due to the different kinds of scaling
> Christoph> applied to the clock frequency to produce the ITC frequency.
>
> No, I think they're precisely because you linked the program dynamically.
> Try linking it statically. I'm fairly confident you'll get the
> same/very similar numbers as I did.
When I link it statically the fastcall handler is not used and the numbers
are much higher. Maybe we are using different glibcs? This is with SUSE
SLES9.
next prev parent reply other threads:[~2004-08-03 21:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 3:52 Timer updates revision 7 (asm sets predicates/various fixes) Christoph Lameter
2004-07-30 4:23 ` David Mosberger
2004-07-30 14:45 ` Jack Steiner
2004-07-30 15:30 ` Christoph Lameter
2004-07-30 15:34 ` Christoph Lameter
2004-08-02 9:32 ` David Mosberger
2004-08-02 9:36 ` David Mosberger
2004-08-03 2:33 ` christoph
2004-08-03 18:06 ` David Mosberger
2004-08-03 21:06 ` Christoph Lameter [this message]
2004-08-04 8:31 ` 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=Pine.LNX.4.58.0408031405310.21526@server.home \
--to=christoph@lameter.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