[En-Nut-Discussion] TCP vs. Memory - a solution

Michael Jones Michael.e.Jones at web.de
Wed Oct 21 10:49:10 CEST 2009


Harald Kipp wrote:

> I committed the code to SVN trunk.

I've check Harald's changes and find them very neat and my tests here show
only positive results! 

In my opinion this change should resolve a lot of strange und random
crashes, disconnects and other connection problem. (I know this has been
haunting *me* for quite some while).

Thanks!

Cu,
Michael

-----Original Message-----
From: en-nut-discussion-bounces at egnite.de
[mailto:en-nut-discussion-bounces at egnite.de] On Behalf Of Harald Kipp
Sent: Dienstag, 20. Oktober 2009 20:51
To: Ethernut User Chat (English)
Subject: Re: [En-Nut-Discussion] TCP vs. Memory - a solution

Harald Kipp wrote:

> After a short time Nut/OS heap space went down to 82 bytes. Wow!

I even got it down to 60 bytes. Without crashing, btw.

Actually Michael's suggestion was only part of the story. Limiting the
buffer for segments following a lost segment was the first task. I made
it global, so it will limit the buffer for all connections.

The second part was the buffer for packets in sequence. During a phone
call with Michael we discussed several strategies. I strongly rejected
his idea to use the filler of the Ethernet frame and suggested a real
window buffer instead. After hanging up I thought about Michael's idea
again and it finally led me to the current solution. If there are at
least 8 packets in the queue with at least one small packet it front,
they will be collected into 1 packet. The great thing here is, that only
a few changes were required.

I committed the code to SVN trunk.

Harald
_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion




More information about the En-Nut-Discussion mailing list