lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-users] Problem with sending big buffers to lwip_write and semaphor


From: Hans . Forsstrom
Subject: [lwip-users] Problem with sending big buffers to lwip_write and semaphoresduring big downloads.
Date: Wed, 11 Apr 2007 10:20:15 +0200


Hello,
I have been using LWIP in a project for a couple of months now and I think I have been able to correct the main part of my bugs :-). We have ported LWIP onto our own software platform, so we had some problems with the porting layer to start with. For the moment we are running version 1.2, but I have also tested 1.1.1 and a newer version directly from CVS. We have created our own ethernet interface that works toward a USB CDC Subset solution, so the problem might be with other parts of our solution.


The first problem is sending big buffers to lwip_write. If I send in a buffer that are bigger then a ethernet frame (3000 bytes) then LWIP will send the first buffer but my second call to write will not work. Attached you will find a log from Wireshark running on a laptop connected via USB to our platform. The laptop are 10.0.01 and our platform has 10.0.0.2.


The other problem is with semaphores. This is quite a small problems as I seems to be able to work around it by streaming smaller amount of data. Anyway, If I connect to a server and starts streaming data over TCP via LWIP. Then everything works fine until about 100 MB of data when our platform assert based on more calls to
sys_sem_signal then to sys_arch_sem_wait.

Have anyone had simular problems and can give me some idea on where the problem might be?


Thank's for the help in advance!


BR,

Hans
******************************
Neither the footer nor anything else in this E-mail is intended to or constitutes an
electronic signature and/or legally binding agreement in the absence of an express
statement or Autoliv policy and/or procedure to the contrary.

This E-mail and any attachments hereto are Autoliv property and may contain legally
privileged, confidential and/or proprietary information. The recipient of this E-mail is
prohibited from distributing, copying, forwarding or in any way disseminating any
material contained within this E-mail without prior written permission from the author.
If you receive this E-mail in error, please immediately notify the author and delete this
E-mail. Autoliv disclaims all responsibility and liability for the consequences of any
person who fails to abide by the terms herein.
******************************

Attachment: tcpip_dump_hangs.pcap
Description: Binary data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]