From: "Barry Wu" <wu_qingbo1969@hotmail.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] how linux support ccnuma system?
Date: Mon, 10 Mar 2003 06:45:24 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709806014@msgid-missing> (raw)
Hi Rich,
Glad to receive your email about EFI.
I have some questions to ask you.
>Some general comments on our experience with using Intel's SAL and PAL
>on our Altix system (up to 64p SSI):
>-The PAL spec specifies whether functions must be called by each CPU, or
> has a system wide effect and may be called by any one CPU. In general
> most all PAL functions operate only on, and retrieve info for, just the
> calling CPU.
>-The SAL spec also specifies this. The SAL spec expects that memory is
> globally accessible. Most SAL functions operate on a shared global
> data structure, and specify that only one CPU need make a call to set
> state for all CPUs.
>-We have found very little problem with PAL & SAL in our global shared
> memory system.
>The right way to figure out your situation is to proceed:
>a) get a detailed spec from your hardware designer as to exactly
> what operations are "propagated" between FSBs, and which software
> has to be responsible for.
I do not know which mean FSBs? Can you give me some explanation?
>b) understand very clearly how physical address space is being shared,
> and the global view each CPU will have. Hardware designs can do
> bizarre things in providing partial sharing. You should argue these
> things are foolish if they are not readily supportable by software.
Which mean provide partial sharing? Can each cpu have its local memory
and do not shared all cpus?
>I hope this is helpful,
Very helpful. Thanks.
Barry
_________________________________________________________________
享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com
reply other threads:[~2003-03-10 6:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-105590709806014@msgid-missing \
--to=wu_qingbo1969@hotmail.com \
--cc=linux-ia64@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