RE: Very long wait on event after TDI_SEND

You shouldn’t change that value in the registry. Remember that it is the
server machine’s delay ack setting that is the issue here.

What I would do is setup a completion routine on your TDI_SEND IRP and
in the completion routine handle any cleanup you need to do.

The only synchronization you need is if you access a shared resource
in the sending thread and the thread that services your completion
routine.

-Jeff

-----Original Message-----
From: Sergey Kipnis [mailto:kipnis@wp.pl]
Sent: Monday, June 23, 2003 1:40 PM
To: NT Developers Interest List
Subject: [ntdev] 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


You are currently subscribed to ntdev as: xxxxx@concord.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
the latest virus scan software available for the presence of computer
viruses.
**********************************************************************