public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew.lunn@ascom.ch>
To: wangwei <wangw@start.com.cn>
Cc: ecos <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] how do you thank about ecos's tcp/ip stack
Date: Thu, 07 Dec 2000 01:41:00 -0000	[thread overview]
Message-ID: <20001207104137.G7689@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <002201c0602f$750ba240$592da8c0@ww.term.star.com.cn>

> Hi all:
>    Are there anybody tell me about the tcp/ip stack of eCos?
>    when I first use the stack which release with v1.3.1,It dumps when pinged
> by a package larger than 1500 bytes.

Actually, thats not a stack issue, but a device driver issue. Its the
generic driver thats throwing an assertion. The basic assumption was
that ethernet packets have a maximum size of 1514 bytes. Packets
longer than this are invalid so the ethernet chip should throw them
away. This assumption was wrong and the i82559 does pass packets up
that are bigger than legal ethernet frames! The driver has now been
modified to detect packets with silly sizes and drop them.

> And then I get the new version from CVS this bug is fixed .But I
> alway feel the tcp/ip stack is not very stable .  Does anybody has
> the same experience with me ?

99% of the code comes from the OpenBSD sources. Thats stable. As
normal, the bits that are specific to eCos have had a few problems. In
terms of the stack thats timer functions, scheduling the stack to run
and select. These have been worked on and and now seem stable. I've
not recently had problems with it. 

You should not consider the stack on its own. The ethernet drivers are
also new, and as you have found, there have been a few minor bugs to
remove. I can only speak for the i82559 driver on the EBSA, but that
is now stable. 

Overall, im happy with the stack and i82559 driver.

        Andrew

  reply	other threads:[~2000-12-07  1:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-07  1:25 wangwei
2000-12-07  1:41 ` Andrew Lunn [this message]
2000-12-07  3:46   ` Hugo Tyson
2000-12-07  1:44 ` Colin Ford

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=20001207104137.G7689@biferten.ma.tech.ascom.ch \
    --to=andrew.lunn@ascom.ch \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=wangw@start.com.cn \
    /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).