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: Raffaele BELARDI <raffaele.belardi@...>
Subject: Re: Re: x86_64 optimization patches for glibc.
Date: Tue, 26 Jul 2005 19:02:35 +0200
Duncan wrote:
>>>>
>>>>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)
> 
> 
> Perhaps it has something to do with the layout of your memory (and BIOS
> configuration), single-channel vs. dual-channel memory access?

I was thinking the same, but moore on the CPU side: the Asus K8V
supports only the 745pin Athon64, which has a single memory channel as
opposed to the 900+ pin (I don't remember the exact number) Athlon64 FX,
which includes dual memory channel.

raffaele
-- 
gentoo-amd64@g.o mailing list


Replies:
Re: Re: x86_64 optimization patches for glibc.
-- Michael Edwards
References:
x86_64 optimization patches for glibc.
-- Simon Strandman
Re: x86_64 optimization patches for glibc.
-- Luke-Jr
Re: x86_64 optimization patches for glibc.
-- Olivier Crete
Re: x86_64 optimization patches for glibc.
-- Luke-Jr
Re: x86_64 optimization patches for glibc.
-- Duncan
Navigation:
Lists: gentoo-amd64: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: x86_64 optimization patches for glibc.
Next by thread:
Re: Re: x86_64 optimization patches for glibc.
Previous by date:
Re: x86_64 optimization patches for glibc.
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.