Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!cornell!rochester!pt.cs.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!<UNAUTHENTICATED>+
From: Richard.Draves@cs.cmu.edu
Newsgroups: comp.os.mach
Subject: Re: mach_port_allocate_name
Message-ID: <0cO=a3K00hsQ92UWIq@cs.cmu.edu>
Date: 26 Jun 91 15:57:55 GMT
References: <BUZ.91Jun24165007@buz.eng.ready.com>
	<MIB.91Jun25133212@geech.gnu.ai.mit.edu>,
	<BUZ.91Jun25192041@buz.eng.ready.com>
Organization: Carnegie Mellon, Pittsburgh, PA
Lines: 15
In-Reply-To: <BUZ.91Jun25192041@buz.eng.ready.com>

Excerpts from netnews.comp.os.mach: 26-Jun-91 Re:
mach_port_allocate_name Greg Buzzard) (1645)

>   A server can arrange, with mach_port_allocate_name, to have port
>   rights correspond directly to addresses of relevant data structures
in
>   its address space, saving a table lookup.
>
>Yuck! :-) I don't see how you can resolve the possibility of multiple
>servers that might want to do this with the same virtual addresses.

Every task has its own port name space, so different servers can
allocate ports with the same name/address for the receive rights.

Rich