From: Luke-Jr <luke-jr@utopios.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] x86_64 optimization patches for glibc.
Date: Tue, 26 Jul 2005 15:40:05 +0000 [thread overview]
Message-ID: <200507261540.06591.luke-jr@utopios.org> (raw)
In-Reply-To: <1122331103.13635.51.camel@cocagne.max-t.internal>
On Monday 25 July 2005 22:38, Olivier Crete wrote:
> On Mon, 2005-25-07 at 22:24 +0000, Luke-Jr wrote:
> > On Saturday 23 July 2005 18:44, Brian Litzinger wrote:
> > > > On Sat, 2005-07-23 at 16:48 +0200, Simon Strandman wrote:
> > > > > Memory to memory copy rate = 1291.600098 MBytes / sec. Block size =
> > > > > Memory to memory copy rate = 2389.321777 MBytes / sec. Block size =
> > >
> > > Memory to memory copy rate = 1302.701782 MBytes / sec. Block size =
> > > Memory to memory copy rate = 2051.979980 MBytes / sec. Block size =
> >
> > Before: Memory to memory copy rate = 557.960449 MBytes / sec. Block size
> > = After: Memory to memory copy rate = 1120.773804 MBytes / sec. Block
> > size =
> >
> > Anyone have a clue why I'm getting half what everyone else gets? o.O
>
> What kind of cpu/ram/motherboard do you have ?
RAM: 2875MB/1002MB (286%) used (I didn't see swapping during the test, tho)
Motherboard: Asus K8V-SE
CPU: AMD Athlon(tm) 64 Processor 3200+ (2202.876 MHz)
On Tuesday 26 July 2005 02:54, Brian Litzinger wrote:
> One of the arguments to memcpy is the clock rate in MHz of *your* CPU.
> Did you adjust it appropriate for your system?
memtst 2200 1000 1048576
so, yes... unless it's expecting the "Intel equivalent" 3200 number...
--
Luke-Jr
Developer, Utopios
http://utopios.org/
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-26 15:42 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 14:48 [gentoo-amd64] x86_64 optimization patches for glibc Simon Strandman
2005-07-23 16:36 ` Allan Wang
2005-07-23 17:08 ` Simon Strandman
2005-07-23 17:30 ` Allan Wang
2005-07-23 18:11 ` Jared Lindsay
2005-07-23 18:19 ` Allan Wang
2005-07-27 10:09 ` netpython
2005-07-27 16:11 ` [gentoo-amd64] " Duncan
2005-07-23 18:44 ` [gentoo-amd64] " Brian Litzinger
2005-07-25 22:24 ` Luke-Jr
2005-07-25 22:38 ` Olivier Crete
2005-07-26 15:40 ` Luke-Jr [this message]
2005-07-26 16:50 ` [gentoo-amd64] " Duncan
2005-07-26 17:02 ` Raffaele BELARDI
2005-07-26 17:49 ` Michael Edwards
2005-07-26 18:42 ` [gentoo-amd64] " Duncan
2005-07-27 0:05 ` [gentoo-amd64] " Sami Samhuri
2005-07-27 2:50 ` Matt Randolph
2005-07-26 2:54 ` [gentoo-amd64] " Brian Litzinger
2005-07-23 16:39 ` Sean Johnson
2005-07-23 22:15 ` Matt Randolph
2005-07-23 22:36 ` Matt Randolph
2005-07-24 1:47 ` Sean Johnson
2005-07-24 3:36 ` Matt Randolph
2005-07-24 5:36 ` Ian McCulloch
2005-07-24 7:42 ` Jared Lindsay
2005-07-24 14:35 ` Simon Strandman
2005-07-24 18:13 ` Jared Lindsay
2005-07-25 20:08 ` Jeremy Huddleston
2005-07-25 21:34 ` Simon Strandman
2005-07-25 22:00 ` Jared Lindsay
2005-07-31 14:24 ` [gentoo-amd64] " Duncan
2005-07-31 14:56 ` Brian Hall
2005-07-31 16:23 ` [gentoo-amd64] " Duncan
2005-07-31 17:42 ` Ben Skeggs
2005-07-31 18:46 ` Jared Lindsay
2005-07-31 18:52 ` Nuitari
2005-08-01 13:51 ` [gentoo-amd64] " Duncan
2005-07-31 19:21 ` [gentoo-amd64] " Simon Strandman
2005-08-01 9:04 ` Jan Jitse Venselaar
2005-08-01 13:45 ` [gentoo-amd64] " Duncan
2005-08-01 17:03 ` Karol Krizka
2005-08-02 10:21 ` [gentoo-amd64] " Duncan
2005-08-02 19:41 ` Matt Randolph
2005-08-02 23:27 ` [gentoo-amd64] hijacked! :) television (was: x86_64 optimization patches for glibc.) Sami Samhuri
2005-08-04 2:28 ` Luke-Jr
2005-08-05 0:28 ` Sami Samhuri
2005-08-05 7:43 ` Arm Suwarnaratana
2005-08-09 10:29 ` [gentoo-amd64] Re: x86_64 optimization patches for glibc Simon Strandman
2005-07-26 17:40 ` [gentoo-amd64] " ardour
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=200507261540.06591.luke-jr@utopios.org \
--to=luke-jr@utopios.org \
--cc=gentoo-amd64@lists.gentoo.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