From: Andrew Walrond <andrew@walrond.org>
To: linux-os@analogic.com
Cc: Andreas Klein <Andreas.C.Klein@physik.uni-wuerzburg.de>,
Sergei Haller <Sergei.Haller@math.uni-giessen.de>,
Andi Kleen <ak@muc.de>, "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org
Subject: Re: solution Re: lost memory on a 4GB amd64
Date: Wed, 27 Oct 2004 18:47:41 +0100 [thread overview]
Message-ID: <200410271847.41827.andrew@walrond.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0410271238180.6872@chaos.analogic.com>
On Wednesday 27 Oct 2004 17:44, linux-os wrote:
>
> Could you please explain how memory is connected to only one
> CPU? I don't think this is possible.
The DIMMS are connected connected to cpu1. cpu2 accesses the ram with the
Hypertransport bus.
See page 9 of ftp://ftp.tyan.com/manuals/m_s2875_102.pdf
>
> Is this board for some new multiple-CPU specification? It can't
> work for SMP (symmetrical multiprocessor specification) unless
> both CPUs can access the same RAM.
They can. Its a sort of castrated NUMA board :)
Andrew Walrond
next prev parent reply other threads:[~2004-10-27 17:56 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 4:48 Sergei Haller
2004-09-16 13:30 ` Andrew Walrond
2004-09-16 13:48 ` Andrew Walrond
2004-09-16 14:09 ` Sergei Haller
2004-09-16 14:28 ` Andrew Walrond
2004-09-16 14:56 ` Sergei Haller
2004-09-16 15:19 ` Andrew Walrond
2004-09-16 15:52 ` Sergei Haller
2004-09-18 14:18 ` Sergei Haller
2004-09-19 20:01 ` Jon Masters
2004-09-19 21:47 ` Sergei Haller
2004-09-19 22:00 ` Jon Masters
2004-09-19 22:19 ` Sergei Haller
2004-09-20 10:26 ` Sergei Haller
2004-09-24 4:38 ` Sergei Haller
2004-09-24 8:15 ` Andrew Walrond
2004-09-24 8:23 ` Sergei Haller
2004-09-24 8:31 ` Andrew Walrond
2004-09-24 8:57 ` Sergei Haller
2004-09-24 9:27 ` Rafael J. Wysocki
2004-09-24 9:41 ` Andrew Walrond
2004-09-24 11:42 ` Sergei Haller
2004-09-24 12:15 ` Andrew Walrond
2004-10-22 8:59 ` Sergei Haller
2004-10-22 9:26 ` Andrew Walrond
2004-10-22 18:24 ` Andi Kleen
2004-10-23 10:02 ` Andreas Klein
2004-10-23 16:43 ` Andi Kleen
2004-10-26 11:25 ` Andreas Klein
2004-10-23 10:26 ` Sergei Haller
2004-10-23 16:49 ` Andi Kleen
2004-10-24 9:53 ` Sergei Haller
[not found] ` <Pine.LNX.4.58.0410271704050.3903@pluto.physik.uni-wuerzburg.de>
2004-10-27 15:39 ` solution " Sergei Haller
2004-10-27 16:05 ` Andreas Klein
2004-10-27 16:17 ` Sergei Haller
2004-10-28 13:32 ` Andreas Klein
2004-10-27 16:44 ` linux-os
2004-10-27 17:47 ` Andrew Walrond [this message]
2004-09-24 11:50 ` Sergei Haller
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=200410271847.41827.andrew@walrond.org \
--to=andrew@walrond.org \
--cc=Andreas.C.Klein@physik.uni-wuerzburg.de \
--cc=Sergei.Haller@math.uni-giessen.de \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=rjw@sisk.pl \
/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
Powered by JetHome