From: Dag Nygren <dag@newtech.fi>
To: Ciprian <cipicip@yahoo.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, dag@newtech.fi
Subject: Re: kernel 2.6 speed
Date: Sun, 24 Jul 2005 22:47:37 +0300 [thread overview]
Message-ID: <20050724194737.30199.qmail@dag.newtech.fi> (raw)
In-Reply-To: Message from Ciprian <cipicip@yahoo.com> of "Sun, 24 Jul 2005 12:12:11 PDT." <20050724191211.48495.qmail@web53608.mail.yahoo.com>
> In windows were performed about 300 millions cycles,
> while in Linux about 10 millions. This test was run on
> Fedora 4 and Suse 9.2 as Linux machines, and Windows
> XP Pro with VS .Net 2003 on the MS side. My CPU is a
> P4 @3GHz HT 800MHz bus.
>
> I published my little test on several forums and I
> wasn't the only one who got these results. All the
> other users using 2.6 kernel obtained similar results
> regardless of the CPU they had (Intel or AMD).
Looking at the gcc-produced code from youe test program I
can see the floating point math beeing optimized away all
together as you are not using the result and the rest more
or less boils down to the call to time() and a few moves
and compares of the time values.
In other words it seems like you are testing the efficiency of
the time() function...
BRGDS
Dag
next prev parent reply other threads:[~2005-07-24 19:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-24 19:12 Ciprian
2005-07-24 19:41 ` Brice Goglin
2005-07-24 19:47 ` Dag Nygren [this message]
2005-07-24 20:40 ` Puneet Vyas
2005-07-24 21:03 ` Florin Malita
2005-07-24 22:49 ` Lee Revell
2005-07-25 19:52 ` Bill Davidsen
2005-07-24 21:46 ` Jan Engelhardt
2005-07-24 23:47 ` Alan Cox
2005-07-25 4:10 ` Florin Malita
2005-07-25 5:18 ` Willy Tarreau
2005-07-25 6:47 ` Ciprian
2005-07-26 5:55 ` cutaway
2005-07-26 19:45 ` Florin Malita
2005-08-03 15:31 Henrik Holst
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=20050724194737.30199.qmail@dag.newtech.fi \
--to=dag@newtech.fi \
--cc=cipicip@yahoo.com \
--cc=linux-kernel@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
Powered by JetHome