Not "probably" ;^) Effectively tcp_sent() is called when an ACK arrives.
That is what the docs say and how TCP works.
No need to do it timely, though.
Perhaps the idea is something like this:
Oh, I need to send something now.
Is there any room ?
Yes -> Fill as much buffer as I can
Re: [lwip-users] Raw TCP Client - wait for ACK after each packet
causes slowdown
Without a _small_ and clear example (I won't browse your entire code) and a
proper capture file I can't help you further. Perhaps someone else jumps in.
___
lwip-users mai
Without a _small_ and clear example (I won't browse your entire code)
and a proper capture file I can't help you further. Perhaps someone else
jumps in.
___
lwip-users mailing list
lwip-users@nongnu.org
- wait for ACK after each packet
causes slowdown
Have you read the docs ? the wiki ?
you can pump into the buffer as much as it fits into the buffer.
TCP can send as much as its window allows, and will certainly need ACKs to keep
sending thereafter.
http://lwip.wikia.com/wiki/Raw/TCP
--
Sergio R
Have you read the docs ? the wiki ?
you can pump into the buffer as much as it fits into the buffer.
TCP can send as much as its window allows, and will certainly need ACKs
to keep sending thereafter.
http://lwip.wikia.com/wiki/Raw/TCP
--
Sergio R. Caprile, Human Being, Bs.As., Argentina
Hello!
I wrote a TCP client (on STM32 microprocessor) that should send a large amount
of data to a Windows host PC (TCP server). However, this is quite slow because
the client waits for the ACK message after each transmitted packet.
Data is sent like this:
Client connects to Server
Sends data
