public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "John Zulauf" <john.zulauf@amd.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Jordan Crouse" <jordan.crouse@amd.com>,
	linux-kernel@vger.kernel.org, info-linux@ldcmail.amd.com
Subject: Re: AMD Geode GX/LX Support (Refreshed)
Date: Thu, 03 Nov 2005 12:16:48 -0700	[thread overview]
Message-ID: <1131045408.5959.27.camel@zoom.amd.com> (raw)
In-Reply-To: <LYRIS-4271-75416-2005.11.01-16.24.38--john.zulauf#amd.com@whitestar.amd.com>

Alan,

I've done the benchmarking of the 3DNOW and non-3DNOW configured Geode
GX/LX.  This was done by extracting the kernel memcpy code into a
userland test application.  Time measurement were made using rdtsc.

The results are averaged over 4 test runs on a Geode LX. The tot_memcpy
is the total CPU clocks to run every memcpy from len = 2
through 4095 four times.  For the 3DNOW version this even includes the 

if (len <512){  __memcpy ... } 

escape found in the kernel __memcpy3d mmx_memcpy wrapper function. 

               No 3DNOW w/ 3DNOW  improvement
tot_memcpy      4635754 4360040  5.9%
tot_copy_page      2324    1853 20.3%
tot_clear_page     4398    1427 67.5%

These are meaningful improvement and the 3DNOW config should be enabled
for Geode GX and LX.

Best Regards,

John Zulauf

On Tue, 2005-11-01 at 23:53 +0000, Alan Cox wrote:
> On Maw, 2005-11-01 at 16:10 -0700, Jordan Crouse wrote:
> > in my app, I think we should leave X86_USE_PPRO_CHECKSUM enabled for Geode
> > GX/LX.
> 
> Definitely.
> 
> 
> 
> 
> ---
> You are currently subscribed to info-linux@geode.amd.com
> as: john.zulauf@amd.com
> To unsubscribe send a blank email to:
> leave-info-linux-4271N@whitestar.amd.com
-- 
John Zulauf
Senior MTS, Embedded Core Software
Advanced Micro Devices, Inc.
1351 So Sunset St
Longmont, CO 80501

303 774 5166 office
303 774 5801 fax



       reply	other threads:[~2005-11-03 19:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
     [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
2005-11-01 23:53       ` Alan Cox

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=1131045408.5959.27.camel@zoom.amd.com \
    --to=john.zulauf@amd.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=info-linux@ldcmail.amd.com \
    --cc=jordan.crouse@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox