From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: "J.A. Magall?n" <jamagallon@ono.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Opteron box and 4Gb memory
Date: Mon, 5 Nov 2007 13:50:40 -0500 [thread overview]
Message-ID: <20071105185040.GF27646@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20071105194521.5fc0ec71@werewolf>
On Mon, Nov 05, 2007 at 07:45:21PM +0100, J.A. Magall?n wrote:
> Well, problem solved...
>
> I'm going to kill all pc assemblers in the world... Someone should teach them
> to learn mauals before assembling anything but a power chord.
>
> The memory was not paired, so the motherboard was not interleaving the access.
> With no inter-node but with inter-module interleaving, and a couple 1Gb sticks
> for each processor now I get something like:
>
> cicely:~/bn> bn
> name: cicely.cps.unizar.es
> arch: x86-64
> proc: 4 x x86_64 @ 2200 MHz
> ram: 3555 Mb
> os: unx, Linux, 2.6.23.1-desktop-1mdv
> cc: gcc-4.3.0
> vector size : 8 x 1024 x 1024
> allocation: 0.02 ms
> int scl add: .......... 60.56 ms, 138.52 Mips | 62.96 Mips /GHz
> int scl mul: .......... 59.34 ms, 141.36 Mips | 64.26 Mips /GHz
> flt scl add: .......... 59.01 ms, 142.16 Mflops | 64.62 Mflops/GHz
> flt vec add: .......... 14.79 ms, 567.06 Mflops | 257.75 Mflops/GHz
> flt scl mul: .......... 59.02 ms, 142.12 Mflops | 64.60 Mflops/GHz
> flt vec mul: .......... 14.82 ms, 566.19 Mflops | 257.36 Mflops/GHz
> total: 5019.86 ms
>
> Much better, but not like the other opteron box.
>
> My processors are higher than Rev E0, because the BIOS does not let me choose
> the 'software' hole. If I activate the 'hardware hole', I see al the memory
> I can:
>
> cicely:~/bn> free
> total used free shared buffers cached
> Mem: 3640628 214496 3426132 0 21240 84184
> -/+ buffers/cache: 109072 3531556
> Swap: 4200988 0 4200988
>
> 3.64 Gb. The rest is eaten by the graphics card, as I could read in the
> AMD site. Don't know if mem=4096 to boot the kernel would help, even if it
> is possible (don't think so, as it looks like a BIOS mis-feature).
> The ram is DDR 400.
The video card is stealing 300MB of ram? What for? What does the mtrr
and e820 map look like with the hardware hole enabled?
> Anyways, can I trust what dmidecode says ? I installed the ram as the board
> manual said in banks 1A+1B (not 2A+2B) for each processor, but this program
> says this:
>
> BANK0 64Mb BANK4 64Mb
> BANK1 64Mb BANK5 64Mb
> BANK2 1024Mb BANK6 1024Mb
> BANK3 1024Mb BANK7 1024Mb
>
> I would always have thought that BANK0 would be slot 1A in first processor,
> but it looks like not...
> And where do the 64 Mb blocks come from ?
Well if you ahve 4 sticks of 1GB, then I would hope they are installed
as a pair for each CPU so that both CPUs can have dual channel ram
directly connected.
I have no idea where the 64Mb comes from.
--
Len Sorensen
next prev parent reply other threads:[~2007-11-05 18:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 21:09 J.A. Magallon
2007-10-25 21:58 ` H. Peter Anvin
2007-10-25 22:44 ` J.A. Magallón
2007-10-26 8:08 ` Arne Georg Gleditsch
2007-10-25 22:45 ` Rafael J. Wysocki
2007-11-04 23:18 ` J.A. Magallón
2007-11-05 18:10 ` Lennart Sorensen
2007-11-05 18:45 ` J.A. Magallón
2007-11-05 18:50 ` Lennart Sorensen [this message]
2007-11-05 23:03 ` J.A. Magallón
2007-11-08 18:08 ` Lennart Sorensen
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=20071105185040.GF27646@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=jamagallon@ono.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
all inboxes | Powered by JetHome®