Re: [lwip-users] Race condition with lwIP-1.3.2 in PXELINUX-4.10-pre16+ on VMware/KVM platforms

2011-10-12 Thread goldsi...@gmx.de
Gene Cumm wrote: For the past several months, Syslinux has been trying to integrate lwIP into PXELINUX. At the moment, there appears to be a bug of some sort when using VMware platforms or some KVM platforms. Over the last few weeks, I've been working with hpa and trying to add additional

[lwip-users] Race condition with lwIP-1.3.2 in PXELINUX-4.10-pre16+ on VMware/KVM platforms

2011-10-12 Thread Gene Cumm
For the past several months, Syslinux has been trying to integrate lwIP into PXELINUX. At the moment, there appears to be a bug of some sort when using VMware platforms or some KVM platforms. Over the last few weeks, I've been working with hpa and trying to add additional debug checks to trace th

Re: [lwip-users] Callback when get any IP or ICMP packet?

2011-10-12 Thread narke
On 10 October 2011 12:29, Simon Goldschmidt wrote: >  Paul Archer wrote: > >>> As i said, a good example for using a raw pcb is in the ping app. Have you >>> had a look at it? In the receive callback, just always return 0, then no >>> packet will get changed. >> >> I thought I would paste a lin

Re: [lwip-users] TCP bandwidth limited by rate of ACKs

2011-10-12 Thread goldsi...@gmx.de
Mason wrote: Bill Auerbach wrote: That 7.4% for memcpy is a direct hit on throughput. You're seeing a breakdown of total CPU time. How much of that 7+% for memcpy comes out of the total time used by lwIP? I think you'll find that to be a much larger hit and a large contributor to lower bandw

Re: [lwip-users] TCP bandwidth limited by rate of ACKs

2011-10-12 Thread Mason
Bill Auerbach wrote: > That 7.4% for memcpy is a direct hit on throughput. You're seeing a > breakdown of total CPU time. How much of that 7+% for memcpy comes out of > the total time used by lwIP? I think you'll find that to be a much larger > hit and a large contributor to lower bandwidth. B

Re: [lwip-users] TCP bandwidth limited by rate of ACKs

2011-10-12 Thread Bill Auerbach
That 7.4% for memcpy is a direct hit on throughput. You're seeing a breakdown of total CPU time. How much of that 7+% for memcpy comes out of the total time used by lwIP? I think you'll find that to be a much larger hit and a large contributor to lower bandwidth. >OS21 profile analysis for main

Re: [lwip-users] TCP bandwidth limited by rate of ACKs

2011-10-12 Thread Mason
Kieran Mansley wrote: > Mason wrote: > >> In the UDP test, any frame larger than 1500 bytes was >> not passed to lwip. The bogus ACK was sent directly >> from the RX context instead. > > OK, I'm not at all surprised that there is a big difference between the > performance of that test, and the T

[lwip-users] ERR_CLSD error after a fixed number of read/write

2011-10-12 Thread Damiano Grechi
Hi, I'm using LwIP and FreeRTOS to develope a simple client/server application with STM3220G board. The client (running on PC) connects to server and then sends a message every 2 seconds. The server (running on STM3220G board) processes the incoming message and replies with an appropriate response