* [ECOS] how do you thank about ecos's tcp/ip stack @ 2000-12-07 1:25 wangwei 2000-12-07 1:41 ` Andrew Lunn 2000-12-07 1:44 ` Colin Ford 0 siblings, 2 replies; 4+ messages in thread From: wangwei @ 2000-12-07 1:25 UTC (permalink / raw) To: ecos 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 .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 ? thanks! ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ECOS] how do you thank about ecos's tcp/ip stack 2000-12-07 1:25 [ECOS] how do you thank about ecos's tcp/ip stack wangwei @ 2000-12-07 1:41 ` Andrew Lunn 2000-12-07 3:46 ` Hugo Tyson 2000-12-07 1:44 ` Colin Ford 1 sibling, 1 reply; 4+ messages in thread From: Andrew Lunn @ 2000-12-07 1:41 UTC (permalink / raw) To: wangwei; +Cc: ecos > 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ECOS] how do you thank about ecos's tcp/ip stack 2000-12-07 1:41 ` Andrew Lunn @ 2000-12-07 3:46 ` Hugo Tyson 0 siblings, 0 replies; 4+ messages in thread From: Hugo Tyson @ 2000-12-07 3:46 UTC (permalink / raw) To: ecos-discuss Andrew Lunn <andrew.lunn@ascom.ch> writes: > "wangwei" <wangw@start.com.cn> wrote: > > 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. That's all true. There was also the change 2000-06-23 Hugo Tyson <hmt@cygnus.co.uk> * src/ecos/support.c (cyg_net_mbuf_alloc, cyg_kmem_init): Align the mbuf pool to MSIZE [128] bytes. That way dtom() works, nasty though it is. That's needed for ip reassembly in ip_input.c, when dealing with large icmp-layer packets eg. ping -s 2000 ... in the stack, which fixed a problem with ICMP reassembly, ie. large pings as opposed to excessively large packets on-the-wire. > > 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. Thanks Andrew! ;-> We think it's pretty stable now; there was a major rewrite of the scheduling and timing functions (eCos specific parts) in August, which added greatly to reliability, a couple of minor bugfixes to that in September and since then mostly changes to our automated test system - fixing the tests rather than fixing the stack, I mean; and fixes to the tftp_server which is NOT part of the OpenBSD sources, but written from scratch initially as a utility and example program, since modified to be pretty much bullet-proof as we came to depend on it in various ways. We're continually running extensive automated tests (as described by AlexS in a message here recently) of the network stack, and the few failures we get are problems with the tests or the configuration of the test farm and associated machines, not with the network stack itself. No true problems have been revealed so far. - Huge ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ECOS] how do you thank about ecos's tcp/ip stack 2000-12-07 1:25 [ECOS] how do you thank about ecos's tcp/ip stack wangwei 2000-12-07 1:41 ` Andrew Lunn @ 2000-12-07 1:44 ` Colin Ford 1 sibling, 0 replies; 4+ messages in thread From: Colin Ford @ 2000-12-07 1:44 UTC (permalink / raw) To: wangwei; +Cc: Ecos Mailing List Hi Wangwei, I've been using the new cvs version of the tcp/ip statck and found it to be very reliable. I've used it for ping tests, flooding, SNMP and Serving web pages. Seems fine to me. Col. wangwei wrote: > 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 .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 ? > thanks! -- =========================================== Colin Ford PipingHot Networks Software Engineer +44 (0)1364 655510 ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2000-12-07 3:46 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2000-12-07 1:25 [ECOS] how do you thank about ecos's tcp/ip stack wangwei 2000-12-07 1:41 ` Andrew Lunn 2000-12-07 3:46 ` Hugo Tyson 2000-12-07 1:44 ` Colin Ford
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).