This is the mail archive of the ecos-discuss@sourceware.cygnus.com mailing list for the eCos project. See the eCos home page for more information.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
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