This is the mail archive of the
ecos-discuss@sourceware.cygnus.com
mailing list for the eCos project.
Re: eCos TCP/IP stack
- To: naidup at dsil dot danlawinc dot com
- Subject: Re: [ECOS] eCos TCP/IP stack
- From: Bart Veer <bartv at redhat dot com>
- Date: Thu, 11 May 2000 13:50:01 +0100
- CC: ecos-discuss at sourceware dot cygnus dot com
- References: <E1BAE8F29762D3119AB000508B441B3605BC1F@agni.dsil.danlawinc.com>
- Reply-to: bartv at redhat dot com
>>>>> "paidi" == Akkala Naidu P <naidup@dsil.danlawinc.com> writes:
paidi> i have worked on LINUX tcp/ip stack.
paidi> i would like to get docs on "eCos TCP/IP networking stack".
paidi> Because of limited resources in eCos , there should be
paidi> difference between genarelized TCP/IP stack and eCos TCP/IP
paidi> stack.
Some documentation is currently available at
http://sourceware.cygnus.com/ecos/tcpip/
You can also consult standard references, e.g. "TCP/IP illustrated" by
W. Richard Stevens.
Please note that this stack is a straightforward port of the BSD
stack. This has a number of advantages:
1) robustness - the code has been around for a long time (although if
you look through the ecos-discuss archives you will note that there
are still some concurrency issues being resolved, the current
release is only a beta).
2) full functionality.
3) the stack should provide pretty good performance.
4) open source. The code is freely available.
However there is also the disadvantage that the stack has not been
designed or optimized specifically for embedded systems. In particular
its memory footprint may be uncomfortably large for some (but by no
means all) embedded systems. In such cases you may be better off
investigating alternative embedded stacks from commercial vendors.
eCos has been designed as a component architecture, you just combine
various packages to meet the needs of your application. The TCP/IP
stack provided on sourceware.cygnus.com is just an add-on package, it
should be possible to install and use alternative stacks. Such stacks
may well have a smaller footprint, but there is likely to be a cost in
terms of e.g. functionality or performance, and there are likely to be
money costs involved as well.
Bart Veer // eCos net maintainer