. Caprile scapr...@gmail.com
To: lwip-users@nongnu.org
Subject: Re: [lwip-users] Retransmit too quick?
Message-ID: 559ff369.3050...@gmail.com
Content-Type: text/plain; charset=utf-8
The RAW API is event driven code.
The ACK is handled as an ACK by lwIP. This means the window is updated,
the sent pbufs
So I don't understand why calling sys_check_timeouts without any
delay yields a poorer performance than calling it or tcp_tmr at 250ms
pace.
Neither do I.
Either your port is broken or your code is not properly written and this
condition masks that out.
I think tcp_sent callback is
have some problem in the port
On 7/10/2015 10:20 AM, lwip-users-requ...@nongnu.org wrote:
--
Message: 2
Date: Fri, 10 Jul 2015 09:22:14 -0300
From: Sergio R. Caprilescapr...@gmail.com
To:lwip-users@nongnu.org
Subject: Re: [lwip-users] Retransmit too quick?
Message-ID
The RAW API is event driven code.
The ACK is handled as an ACK by lwIP. This means the window is updated,
the sent pbufs are freed, and you can send data again.
You can't send more data until you receive an ACK for your window size.
You can't queue more data until lwIP frees pbus (when you receive
On 7/7/2015 12:00 PM, lwip-users-requ...@nongnu.org wrote:
--
Message: 5
Date: Mon, 06 Jul 2015 17:13:34 -0300
From: Sergio R. Caprile scapr...@gmail.com
To: lwip-users@nongnu.org
Subject: Re: [lwip-users] Retransmit too quick?
Message-ID: 559ae16e.2020
Subject: Re: [lwip-users] Retransmit too quick?
Message-ID: 559ae16e.2020...@gmail.com
Content-Type: text/plain; charset=utf-8
Again, you should check how you are handling timers in your port.
sys_check_timeouts() needs a consistent time base, it expects you
provide a sys_now() function which returns
Again, you should check how you are handling timers in your port.
sys_check_timeouts() needs a consistent time base, it expects you
provide a sys_now() function which returns time in milliseconds.
You should call sys_check_timeouts() from your main loop as frequently
as possible so it does its
Hi, Sergio,
Thank you for your time!
I am not calling any raw api from interrupts and I don't use RTOS.
I include the pseudo codes below. (Note: In my codes, only one TCP connection
is allowed)
A) The following codes works, but I still get the (too quick) retransmit
problem after long run,
If you are using the raw api and no RTOS, then your port should (must)
be calling the lwIP timers function and you don't have to do anything
with timers
(that is what I meant by a broken timer implementation).
Your main should be something like
while(1){
Yes, looks like that to me.
Perhaps you have a broken timer implementation and it is expiring ahead
of time ?
Looks like a glitch in a real-time system.
--
___
lwip-users mailing list
lwip-users@nongnu.org
Hi all,
I ran into a problem with lwip 1.4.1. For some reason, lwip decides to
retransmit package immediately, without waiting for the ACK for the receiver
The Wireshark captures for the moment (16KB only) can be downloaded from
11 matches
Mail list logo
