From: Marc Gonzalez-Sigler <marc.gonzalez-sigler@inria.fr>
To: linux-ia64@vger.kernel.org
Subject: Re: Consistency problem on IPF
Date: Mon, 12 Jul 2004 12:01:15 +0000 [thread overview]
Message-ID: <40F27D8B.6010202@inria.fr> (raw)
In-Reply-To: <40F2562C.10208@inria.fr>
Erich Focht wrote:
> On Monday 12 July 2004 13:12, Duraid Madina wrote:
>
>> For the record, on HP-UX 11.23 the standard deviation is down around
>> 0.1s for NP0, 512. For N\x1024, it's basically zero. This is on a 2-way
>> 1.5G/6M system.
>
> Which page-size was the testcode using? HPUX is more flexible here due
> to different usage of the TLB.
>
> What compiler? The initial mail sounded like gcc has been used. I'd
> expect a reasonable (i.e. optimizing) compiler to recognize the
> trivial matrix-matrix multiply pattern and replace it by highly
> optimized code. Which would reduce the problems...
(For the record, I tried gcc-3.3.4 and orcc-2.1)
Perhaps I was not clear enough. I used matrix-matrix multiply only as an
example. My real problem is the non-deterministic behavior.
Say I tile the main loop nest. I want to compare the execution time of
the original, untiled program and the execution time of the modified,
tiled program.
If the original version completes in 1 second 80% of the time, and the
modified version completes in 0.5 seconds 80% of the time, but 2 seconds
20% of the time, then, if I am unlucky, I might eliminate an excellent
candidate. This is why I need the execution times of a given program to
be consistent.
I have looked at /usr/src/linux/Documentation/vm/hugetlbpage.txt and I
will try it if there are no better solutions.
--
Regards, Marc
next prev parent reply other threads:[~2004-07-12 12:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 9:13 Consistency problem on IPF Marc Gonzalez-Sigler
2004-07-12 10:06 ` Erich Focht
2004-07-12 11:12 ` Duraid Madina
2004-07-12 11:24 ` Erich Focht
2004-07-12 11:39 ` Marc Gonzalez-Sigler
2004-07-12 12:01 ` Marc Gonzalez-Sigler [this message]
2004-07-12 20:37 ` David Mosberger
2004-07-12 21:49 ` Duraid Madina
2004-07-12 22:05 ` David Mosberger
2004-07-12 22:08 ` Rich Altmaier
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=40F27D8B.6010202@inria.fr \
--to=marc.gonzalez-sigler@inria.fr \
--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