From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,b95a522100671708
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news1.google.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Nick Roberts <nick.roberts@acm.org>
Newsgroups: comp.lang.ada
Subject: Re: For the AdaOS folks
Date: Wed, 5 Jan 2005 13:14:40 +0000
Message-ID: <gemini.i9ui4g003dg2300z4.nick.roberts@acm.org>
References: <Gq2dnUK90vVhBVLcRVn-1w@gbronline.com>
 <gemini.i9ih0y000ys1c02s4.nick.roberts@acm.org>
 <1PTAd.1218$0y4.421@read1.cgocable.net>
 <1vemlj8wqr9ea$.qyecszhsmtqa$.dlg@40tude.net>
 <J1WAd.1244$0y4.989@read1.cgocable.net>
 <1b48kdfqsk3mw.7gajq12fsa82.dlg@40tude.net>
 <KKaBd.3134$0y4.3044@read1.cgocable.net>
 <rnpnk8lhy0dy$.1m9qo6kbu5art$.dlg@40tude.net>
 <52fBd.42256$nV.1324414@news20.bellglobal.com>
 <33li96F422q0fU1@individual.net>
 <b1hBd.44026$nV.1358305@news20.bellglobal.com>
 <33qh7eF42pn2fU1@individual.net>
 <gemini.i9tfbx00nu4at00dc.nick.roberts@acm.org>
 <CrJCd.14979$0y4.5776@read1.cgocable.net>
Content-Type: text/plain; charset=us-ascii
X-Trace: individual.net IEHzhf+DzXfd/yXPCxhHbQYKzuHD+0LTNMfNbaiEHcV0NZf4g=
X-Orig-Path: not-for-mail
User-Agent: Gemini/1.45d (Qt/3.3.2) (Windows-XP)
Xref: g2news1.google.com comp.lang.ada:7475
Date: 2005-01-05T13:14:40+00:00
List-Id: <comp.lang.ada>

"Warren W. Gay VE3WWG" <ve3wwg@NoSpam.cogeco.ca> wrote:

> ...
> How is this "IPC service key" different than a Mach port? What you
> describe sounds just like Mach RPC (with or without migrating-threads).

I think there are quite a lot of differences in the details. Certainly
thereare similarities.

> ...
> How does this differ from Mach using its ports to map in regions of
> memory?

AdaOS regions are more flexible, in that they can exist outside any process
address space, they can be bigger than 4 MiB, and they can be partially
mapped into address spaces. Different regions can have a different memory
managers.

> It sounds pretty much deja-Mach to me, which is ok. What I have trouble
> understanding is the need for new names.

The basic design for Bachar predates anything (I know of) published about
Mach. I have stuck to the terminology I have used for all the years I have
been evolving the design of Bachar. This design is significantly different
to Mach.

-- 
Nick Roberts