lwip-users
[Top][All Lists]
Advanced

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

[lwip-users] RE: [lwip] tcp_output() and driver errors


From: Troy \(Office PC\)
Subject: [lwip-users] RE: [lwip] tcp_output() and driver errors
Date: Wed, 08 Jan 2003 23:24:07 -0000

Actually, during testing ( Iwas testing our proprietary stack against
lwip for kicks and giggles) I had the exact same problem.  Me and the
rest of our team played with the setup and eventually the error went
away.
Troy redcellx

-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of Holger
Fried
Sent: Monday, October 14, 2002 11:24 AM
To: Lwip (E-Mail)
Subject: [lwip] tcp_output() and driver errors

Hi,

I have one questions:

Is it right, that if my ethernet driver returns an error after a write()

call, for example its sendqueue is full, the tcp-layer will recognize
this 
first, when a ACK_TIME_OUT occurs? Shouldn't the stack instead keep the 
data in the unsent-queue return the error to the application and wait
until 
the driver has enough  space for the packet? Or even better the driver 
calls tcp_output after each TX Confirmation.    
[This message was sent through the lwip discussion list.]

[This message was sent through the lwip discussion list.]




reply via email to

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