Only for TDI filter guru

Home Forums Discussions General Discussion Only for TDI filter guru

This topic contains 3 replies, has 3 voices, and was last updated by  Taras 13 years ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #4896

    Vijender
    Participant

    Hi,

    I have written a TDI filter driver. I works fine except for some conditions.
    The problematic area is receive event handler. TDI documentation in DDK seems to be not updated since first version of NT. The way recv event handler behaves is not-understandable.

    I believe I am at the verge of completing my driver. Only at some point AFD refuses to accept the data and TCP don’t passes me any data. My driver doesn’t have any control. I can’t even guess, what is the problem with my recv event handler.

    If any TDI guru is reading this mail, please contact me. I am in a disaster.

    And ya, its not a simple TDI filter driver. Its a buffered TDI filter driver.

    Regards
    Vijender

    #5681

    GeN
    Participant

    @vijender wrote:

    Hi,

    And ya, its not a simple TDI filter driver. Its a buffered TDI filter driver.

    What do you mean ?

    #5682

    Vijender
    Participant

    I should have explained this point….
    Generally filter drivers dont buffer data. If data is not accepted by upper driver, the filter driver also rejects the data.
    In my case I buffer the data till my buffer is full. After that I start rejecting the data from TCP. Because of buffering I have to do lot of bookkeeping and handle various situation that might occur related to data-reception using TDI_RECEIVE irp and ClientEventReceive.

    Hope I make it clear.

    Regards
    Vijender

    #5683

    Taras
    Participant

    ClientEventChainedReceive
    ClientEventReceiveExpedited
    Do you hook this callback handlers?

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.