From: Sami Samhuri <sami@no-eff-eks.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: x86_64 optimization patches for glibc.
Date: Tue, 26 Jul 2005 17:05:01 -0700 [thread overview]
Message-ID: <20050727000501.GB4009@no-eff-eks.com> (raw)
In-Reply-To: <pan.2005.07.26.16.49.59.697555@cox.net>
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
* On Tue Jul-26-2005 at 09:50:00 AM -0700, Duncan said:
[...]
> Of course, that's just supposition, here. If those with the 1100/2200
> rates would confirm whether they are running in dual-channel memory mode,
> as I suspect, and you confirm that you are running single-channel mode, as
> I am, it'll pretty much confirm that supposition, however.
glibc-2.3.5 (patched)
gentoo-sources-2.6.12-r4
linux-headers-2.6.11-r2
2x Opteron 246 (2GHz)
2x 512M, on processor #0 (dual channel)
% ./a.out 2000 5000 1048576
Memory to memory copy rate = 1367.611206 MBytes / sec. Block size = 1048576.
% ./a.out 4000 5000 1048576
Memory to memory copy rate = 2822.960693 MBytes / sec. Block size = 1048576.
Since only 1 processor is used in this test I'm not sure which processor
speed I should use, and hence which result is accurate. In any case they
take the same amount of time, ~3.7s.
--
Sami Samhuri
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-27 1:48 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
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 ` Sami Samhuri [this message]
2005-07-27 2:50 ` [gentoo-amd64] " 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=20050727000501.GB4009@no-eff-eks.com \
--to=sami@no-eff-eks.com \
--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