From: Tim Wright <timw@splhi.com>
To: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Cc: Pauline Middelink <middelin@polyware.nl>,
linux-kernel@vger.kernel.org, jmerkey@timpanogas.org
Subject: NUMA and SCI [was Re: bigphysarea support in 2.2.19 and 2.4.0 kernels]
Date: Fri, 22 Dec 2000 11:37:29 -0800 [thread overview]
Message-ID: <20001222113729.A8972@scutter.internal.splhi.com> (raw)
In-Reply-To: <20001221144247.A10273@vger.timpanogas.org> <E149DKS-0003cX-00@the-village.bc.nu> <20001221154446.A10579@vger.timpanogas.org> <20001221155339.A10676@vger.timpanogas.org> <20001222093928.A30636@polyware.nl> <20001222111105.B14232@vger.timpanogas.org>
In-Reply-To: <20001222111105.B14232@vger.timpanogas.org>; from jmerkey@vger.timpanogas.org on Fri, Dec 22, 2000 at 11:11:05AM -0700
Hi Jeff,
On Fri, Dec 22, 2000 at 11:11:05AM -0700, Jeff V. Merkey wrote:
[...]
> SCI allows machines to create windows of shared memory across a cluster
> of nodes, and at 1 Gigabyte-per-second (Gigabyte not gigabit). I am
> putting a sockets interface into the drivers so Apache, LVS, and
> Pirahna can use these very high speed adapters for a clustered web
> server. Our M2FS clustered file system also is being architected
> to use these cards.
You're probably aware of this, but SCI allows a lot more then the creation
of windows of shared memory. The IBM NUMA-Q machines (what was Sequent), use
the SCI interconnect to build a single-system image machine with all memory
visible from all "nodes". In fact, all the commercial NUMA machines of which
I am aware have this property (all nodes see and can address all memory). The
non-uniform part of NUMA comes from the potentially differing latency and
speed of different parts of memory (local vs remote in this case).
AFAIK, the work that Kanoj Sarcar has been doing is to enable such machines.
It sounds like you have a different requirement of very high-speed shared
memory between different nodes that can be mapped and unmapped as required.
Do I understand this correctly ? That would make your requirements somewhat
orthogonal to the requirements those of us with NUMA architectures have.
> I will post the source code for the SCI cards at vger.timpanogas.org
> and if you have time, please download this code and take a look at
> how we are using the bigphysarea APIs to create these windows accros
> machines. The current NUMA support in Linux is somewhat slim, and
> I would like to use established APIs to do this if possible.
See above. It may be that you need different APIs anyway.
Regards,
Tim
--
Tim Wright - timw@splhi.com or timw@aracnet.com or twright@us.ibm.com
IBM Linux Technology Center, Beaverton, Oregon
"Nobody ever said I was charming, they said "Rimmer, you're a git!"" RD VI
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-22 20:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-21 21:42 bigphysarea support in 2.2.19 and 2.4.0 kernels Jeff V. Merkey
2000-12-21 21:32 ` Alan Cox
2000-12-21 22:44 ` Jeff V. Merkey
2000-12-21 22:53 ` Jeff V. Merkey
2000-12-22 8:39 ` Pauline Middelink
2000-12-22 8:58 ` Alan Cox
2000-12-22 23:11 ` Albert D. Cahalan
2000-12-23 8:40 ` Eric W. Biederman
2000-12-24 8:59 ` Albert D. Cahalan
2000-12-23 20:11 ` Jes Sorensen
2000-12-24 8:15 ` Albert D. Cahalan
2000-12-22 18:11 ` Jeff V. Merkey
2000-12-22 18:35 ` Jeff V. Merkey
2000-12-22 19:21 ` Andi Kleen
2000-12-22 20:25 ` Jeff V. Merkey
2000-12-22 19:51 ` Pauline Middelink
2000-12-22 21:54 ` Jeff V. Merkey
2000-12-22 21:39 ` Erik Mouw
2000-12-22 23:56 ` Jeff V. Merkey
2000-12-22 19:37 ` Tim Wright [this message]
2000-12-22 20:39 ` NUMA and SCI [was Re: bigphysarea support in 2.2.19 and 2.4.0 kernels] Jeff V. Merkey
2000-12-22 20:30 ` Alan Cox
2000-12-22 21:40 ` Jeff V. Merkey
2000-12-22 21:52 ` Jeff V. Merkey
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=20001222113729.A8972@scutter.internal.splhi.com \
--to=timw@splhi.com \
--cc=jmerkey@timpanogas.org \
--cc=jmerkey@vger.timpanogas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=middelin@polyware.nl \
/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