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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,4045dbe1801294bc
X-Google-Attributes: gid103376,public
From: gwinn@res.ray.com (Joe Gwinn)
Subject: Re: Memory Management Algorithms for Hard Realtime
Date: 1998/02/18
Message-ID: <gwinn-1802981847520001@dh5055200.res.ray.com>#1/1
X-Deja-AN: 326398998
Content-Transfer-Encoding: 7bit
References: <gwinn-1702981912510001@dh5055083.res.ray.com>
 <dewar.887767452@merv>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Organization: Raytheon
Newsgroups: comp.lang.ada
Date: 1998-02-18T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <dewar.887767452@merv>, dewar@merv.cs.nyu.edu (Robert Dewar) wrote:

> Joe said
> 
> <<The clear conclusion of this book is that there are no hard realtime
> memory manager algorithms known, unless one resorts to special hardware.
> The authors are university professors who have studied the field, with a
> 377-page book to show for it.  This lack of suitable algorithms has
> certainly been my personal experience as well, and is why I always
> doggedly stuck to fixed-block allocators.
> >>
> 
> That's a non-sequitur.

Could you explain this?  I don't see your point.


> The book you talk about is, if we believe its title, about *automatic*
> memory management. 
> 
> There are many algorithms for allocating variable sized blocks with
> *manual* allocation/release control that have well defined worst
> case behavior.

I wasn't planning to come along in a missile running the memory management
system, so automatic seems best.  What am I missing?

 
> Nothing you summarize in the rest of your message even hints that
> this is not the case!

Dr. Dewar, I await your list of literature references.


Joe Gwinn