From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Kenneth Porter" <kenneth_porter@kensingtonlabs.com>
To: "Fred Fierling" <fff@microplex.com>
Cc: "ecos-discuss@cygnus.com" <ecos-discuss@cygnus.com>
Subject: Re: [ECOS] TCP/IP Stack for eCos
Date: Tue, 27 Apr 1999 17:55:00 -0000
Message-id: <199904280054.UAA06153@dub-img-ims-2.compuserve.com>
X-SW-Source: 1999-04/msg00029.html

On Tue, 27 Apr 1999 11:07:53 -0700, Fred Fierling wrote:

>A TCP stack that doesn't use malloc? Interesting. Do
>you forbid malloc to avoid problems like memory
>leaks, to guarantee response time, or why?

Perhaps to help in provability? (Ie. guaranteeing the system is valid.)
I expect you could still use buffer pools, instead of a single generic
malloc that handles allocations for all types. In C++ you could use a
class-specific operator new and a private heap for each type.


Kenneth Porter
Kensington Laboratories, Inc.
mailto:kenneth_porter@kensingtonlabs.com
http://www.kensingtonlabs.com