RE: Very long wait on event after TDI_SEND

Hello Jeffrey,

Monday, June 23, 2003, 6:29:57 PM, you wrote:

And what to do with delayed ack? How to change this behaviour from the
driver? Of course, I could change this in registry

=====================================================

Delayed ACKs reduce the number of packets sent on the network. An ACK
is only sent when either of the following occurs:

  • No ACK was sent for the previously received segment.

  • No segment arrives within 200 milliseconds (the default), after
    receiving a segment.

=====================================================

This means that changing ACK delay time to zero is not very good idea.

CJ> Sounds like a delayed ack to me.

CJ> -Jeff

CJ> -----Original Message-----
CJ> From: Sergey Kipnis [mailto:kipnis@wp.pl]
CJ> Sent: Monday, June 23, 2003 12:26 PM
CJ> To: NT Developers Interest List
CJ> Subject: [ntdev] Very long wait on event after TDI_SEND

CJ> Hello,

CJ> I have very strange behaviour in my tdi client. Elapsed time in
CJ> KeWaitForSingleObject after IoCallDriver is almost exactly 200
CJ> milliseconds(usually 199 millisecond but time to time 398 millisecs)!
CJ> What may be the reason of such behaviour?

CJ> Event is set inside completion routine.


Best regards,
Sergey mailto:kipnis@wp.pl