Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-amd64
Navigation:
Lists: gentoo-amd64: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-amd64@g.o
From: Brian Litzinger <brian@...>
Subject: Re: x86_64 optimization patches for glibc.
Date: Mon, 25 Jul 2005 19:54:51 -0700
On Mon, Jul 25, 2005 at 10:24:46PM +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

One of the arguments to memcpy is the clock rate in MHz of *your* CPU.
Did you adjust it appropriate for your system?

-- 
Brian Litzinger
-- 
gentoo-amd64@g.o mailing list


References:
x86_64 optimization patches for glibc.
-- Simon Strandman
Re: x86_64 optimization patches for glibc.
-- Allan Wang
Re: x86_64 optimization patches for glibc.
-- Brian Litzinger
Re: x86_64 optimization patches for glibc.
-- Luke-Jr
Navigation:
Lists: gentoo-amd64: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Re: x86_64 optimization patches for glibc.
Next by thread:
Re: x86_64 optimization patches for glibc.
Previous by date:
Re: Thunderbird - firefox links not opening
Next by date:
Re: x86_64 optimization patches for glibc.


Updated Jun 17, 2009

Summary: Archive of the gentoo-amd64 mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.