public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] strange performance behaviour with floats
Date: Thu, 20 Feb 2003 17:52:43 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805886@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805852@msgid-missing>

>>>>> On Thu, 20 Feb 2003 09:35:02 +0100, Volker Birk <vb@ebios.de> said:

  Volker> On Wed, Feb 19, 2003 at 11:09:36AM -0800, David Mosberger
  Volker> wrote: Hello, I'm wondering about the strange behaviour of
  Volker> the Linux scheduling on my rx5670:

  >> Can you reproduce the behavior with a standard 2.4.xx ia64 kernel
  >> (not with Red Hat's heavily patched kernel)?

  Volker> That is a standard 2.4.xx ia64 kernel (with ia64 patches
  Volker> from kernel.org).

  Volker> bronto:~ # uname -a Linux bronto 2.4.19 #11 SMP Sat Nov 2
  Volker> 18:47:02 CET 2002 ia64 GNU/Linux bronto:~ #

Hmmh, that's really strange.  I assume you realize that your
test-program doesn't really do what the source code suggests (the
loop-body gets optimized away), but regardless the high variation
you're seeing seems wrong.  Are you re-directing the kernel console to
a serial line?  If so, make sure there is no logging activity when the
program runs slower (especially a slow baud-rate can "stall" the
kernel for non-trivial amounts of time).

	--david


  parent reply	other threads:[~2003-02-20 17:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-14  9:02 [Linux-ia64] strange performance behaviour with floats Volker Birk
2003-02-14 10:50 ` Hideki Yamamoto
2003-02-15 11:29 ` Volker Birk
2003-02-19 19:09 ` David Mosberger
2003-02-20 17:52 ` David Mosberger [this message]
2003-02-20 19:59 ` Volker Birk
2003-02-22  2:30 ` 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-105590709805886@msgid-missing \
    --to=davidm@napali.hpl.hp.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