Hi
If you search the list you will find a lot of people with the same
question, it's impossible to tell where your packets are delayed without
you doing some analysis (traces? breakpoints?) but one thing I can say
for sure is that your problem is quite certainly not within lwip. A
common error is to assume that one packet equals one interrupt which
equals one signalled semaphore which equals one processed packet,
whenever you receive a second packet before the previous is processed
you'll be "one packet behind" and experience delays like you describe.
Where did you get your driver?
Best regards
Jens
On 2016-05-11 12:42, Rastislav Uhrin wrote:
Hello,
I need advice and help on one issue with lwip stack version 1.4.1. I
am new to this stack and to networking in general. Nevertheless I have
integrated it to application on Infineon xmc processor together with
FreeRTOS.
Looking on many different examples on the internet and many trial and
error. I am using netconn sockets. Application works!
The only problem is that after some time, better say after exchanging
several 10-100 packets of different sizes, response gets slow. From
2ms down to 2-3seconds. It still works but slow. Same if I use ping.
I tried all possible setting of lwip options but of course since I
don’t have deep insight of what they influence I was not able to
improve this behavior.
I would appreciate if you can give me a hint what could be wrong, what
could I check, how to proceed to debug this strange behavior.
I tried also new version 2.0 of stack but behavior is same.
rum
_______________________________________________
lwip-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________
lwip-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lwip-users
