From: "Jordan Crouse" <jordan.crouse@amd.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, info-linux@ldcmail.amd.com
Subject: Re: AMD Geode GX/LX Support (Refreshed)
Date: Tue, 1 Nov 2005 16:10:51 -0700 [thread overview]
Message-ID: <20051101231051.GM9947@cosmic.amd.com> (raw)
In-Reply-To: <1130711970.32734.13.camel@localhost.localdomain>
> > config X86_USE_PPRO_CHECKSUM
> Does this mean you've now done actual performance analysis on whether
> this is a good idea for Geode GX/LX ?
Ok - here is some data that should put your mind at ease. I pulled
the checksum functions from the kernel, stuck them in userland, and
ran each one N times at a variety of byte sizes (where N=10,000), took the
start and stop times with gettimeofday(), and added it all up. The results
for the Geode LX platfrom are below.
I think the data shows that the ppro checksum is indeed useful on the
Geode LX platform (and the GX should have similar results, since the
pipelines are pretty close). Unless I made a really boneheaded mistake
in my app, I think we should leave X86_USE_PPRO_CHECKSUM enabled for Geode
GX/LX.
Jordan
Starting non-ppro test....
Bytes Time Avg (usec/run)
----------------------------
16 2029 0.202900
32 1666 0.166600
64 2548 0.254800
128 3429 0.342900
256 5268 0.526800
512 8781 0.878100
1024 16031 1.603100
2048 30548 3.054800
4096 59265 5.926500
Total time: 129565
Starting ppro test....
Bytes Time Avg (usec/run)
----------------------------
16 1579 0.157900
32 1655 0.165500
64 1841 0.184100
128 2721 0.272100
256 3582 0.358200
512 5264 0.526400
1024 8900 0.890000
2048 15919 1.591900
4096 29369 2.936900
Total time: 70830
next prev parent reply other threads:[~2005-11-01 23:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <LYRIS-4270-74122-2005.10.28-09.38.17--jordan.crouse#amd.com@whitestar.amd.com>
2005-10-28 15:44 ` [PATCH 1/6] AMD Geode GX/LX Support (Refreshed) Jordan Crouse
2005-10-30 22:39 ` Alan Cox
2005-10-31 15:37 ` Jordan Crouse
2005-11-01 23:10 ` Jordan Crouse [this message]
2005-11-01 23:53 ` Alan Cox
2005-10-28 15:46 ` [PATCH 2/6] " Jordan Crouse
2005-10-28 15:48 ` [PATCH 3/6] " Jordan Crouse
2005-10-28 15:51 ` [PATCH 4/6] " Jordan Crouse
2005-11-09 23:00 ` Bartlomiej Zolnierkiewicz
2005-10-28 15:53 ` [PATCH 5/6] " Jordan Crouse
2005-10-28 15:55 ` [6/6] " Jordan Crouse
2005-11-09 22:25 ` Bartlomiej Zolnierkiewicz
[not found] <LYRIS-4271-75416-2005.11.01-16.24.38--john.zulauf#amd.com@whitestar.amd.com>
2005-11-03 19:16 ` John Zulauf
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=20051101231051.GM9947@cosmic.amd.com \
--to=jordan.crouse@amd.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=info-linux@ldcmail.amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.