From: "Fernando D. Mato Mira" <matomira@iname.com>
To: ecos-discuss@cygnus.com
Subject: Re: [ECOS] TCP/IP Stack for eCos
Date: Wed, 28 Apr 1999 01:14:00 -0000 [thread overview]
Message-ID: <199904280814.KAA16423@link.csem.ch> (raw)
At 05:54 PM 4/27/99 +0700, you wrote:
>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.
Deterministic response time.
Some platforms that we use lack C++ compilers (eg, Analog Devices' SHARC DSP) .
In addiion to that, we could be restricted
to 544 Kbits of RAM (so the maximum program size would be 8K words of
48-bit instructions (leaving aside 8K 40-bit words for data)). That's a $10 DSP.
We just used the non-low-power version where we had the luxury of 1Mbit SRAM
inside. Among several other things, we had networking in it (custom, not IP).
Fernando D. Mato Mira
Real-Time SW Engineering & Networking
Advanced Systems Engineering Division
CSEM - Centre Suisse d'Electronique et de Microtechnique
Jaquet-Droz 1 Email: matomira AT acm DOT org
CH-2007 Neuchatel Phone: +41 (32) 720-5157
Switzerland FAX: +41 (32) 720-5720
http://www.csem.ch/ http://www.vrai.com/ http://ligwww.epfl.ch/matomira.html
next reply other threads:[~1999-04-28 1:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-28 1:14 Fernando D. Mato Mira [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-28 22:04 Prakash R
1999-09-23 15:44 [ECOS] TCP/IP Stack for ECOS Ramana
1999-09-24 9:08 ` Jonathan Larmour
[not found] <Fred>
[not found] ` <Fierling's>
[not found] ` <message>
[not found] ` <of>
[not found] ` <Tue,>
[not found] ` <04>
[not found] ` <May>
[not found] ` <99>
[not found] ` <12:35:31>
[not found] ` <PDT>
1999-05-04 13:51 ` [ECOS] TCP/IP Stack for eCos Jay Lepreau
1999-05-04 17:06 ` Fred Fierling
1999-05-04 17:43 ` Brendan Simon
1999-05-05 1:54 ` Fernando D. Mato Mira
1999-05-04 4:36 Jay Lepreau
1999-05-04 12:36 ` Fred Fierling
1999-04-27 17:55 Kenneth Porter
1999-04-26 7:04 Leonard, Niall
1999-04-23 10:20 Fred Fierling
1999-04-23 12:10 ` Bob Cousins
1999-04-23 13:27 ` Fred Fierling
1999-04-23 16:08 ` Bob Cousins
1999-04-23 17:56 ` Frank W. Miller
1999-04-26 7:02 ` Bart Veer
1999-04-27 6:01 ` Fernando D. Mato Mira
1999-04-27 11:08 ` Fred Fierling
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199904280814.KAA16423@link.csem.ch \
--to=matomira@iname.com \
--cc=ecos-discuss@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).