Returned mail: Host unknown

[Mail Delivery Subsystem]

   ----- Transcript of session follows -----
550 <moose-programmers%davgar%sfu.ca,@uunet.UU.NET>... Host unknown

   ----- Recipients of this delivery -----
   <david%davgar@uunet.UU.NET>
   <moose-programmers%davgar%sfu.ca,@uunet.UU.NET>

   ----- Unsent message follows -----
Received: from dmi.ens.fr by relay2.UU.NET with SMTP 
	(5.61/UUNET-internet-primary) id AA21226; Sat, 13 Mar 93 05:29:08 -0500
Received: from clipper.ens.fr (clipper-gw.ens.fr) by dmi.ens.fr (5.65c8/ULM-1.0)
Received: from brick.ens.fr by clipper.ens.fr (4.1/88/01/19 3.0)
 	id AA14771; Sat, 13 Mar 93 11:29:04 +0100
From: rideau@clipper.ens.fr (Francois-Rene Rideau)
Message-Id: <9303131029.AA14771@clipper.ens.fr>
Subject: Re: memory allocation (djg4)
To: david%davgar@uunet.uu.net
Date: Sat, 13 Mar 93 11:29:03 MET
Cc: @sfu.ca@dmi.ens.fr, moose-programmers%davgar@uunet.uu.net
In-Reply-To: <2b9aed66.davgar@davgar.UUCP>; from "davgar!david" at Mar 8, 93 1:53 am
X-Mailer: ELM [version 2.3 PL11]


>> I firmly believe that at the kernel level, a malloc() style memory
>> allocation interface should not exist.  Using malloc() does not allow
>> any chance for the application to control where the memory blocks are
>> placed.
 There should be different memory managers for all devices/apps/user
programs to match their need. For example very high-level programs
often need a garbage collecting feature, whereas low-level programs
would be only slowed by it. If you don't implement a GC memory manager,
each app will have to do its own, and inter-app object communication
will be made impossible or very, very difficult and slow. If you always
require GC compliancy, that will slow everything, and affect the system
security.
 To me, there should not be only ONE memory manager. Memory management is
not a Kernel feature; there are higher or lower level devices to manage
memory; but they have a standard interface, so that you don't need know
what's its memory manager to access an object.
 We can even build generic memory managers, to transform a low-level
one into a higher-level one by adding each time some features.
 So we start with physical memory, add virtual memory, add word aligned
blocks, add GC, etc. Each time, you can add it in part of the previous
manager; you can add it several times in different parts of the manager;
etc.
		   ,
		Fare