Shaping Howto

Home Forums Discussions Support Portal Shaping Howto

This topic contains 1 reply, has 2 voices, and was last updated by  Vadim Smirnov 9 years, 10 months ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #5146

    netoptima
    Participant

    Hi,

    We are current customer of winpkfilter.

    I am trying to port Automatic Bandwidth Manager on to Windows (from Linux).

    My question is about best shaping approach & duplication of data

    In Linux we have packet_id and we can delay the injection of packet into kernel by calling (after delay) set_verdict(packet_id) function. (little simplified)

    in winpkfilter how to achieve this optimally?

    My plan is to create a simple data structure
    struct PACKET_STORAGE
    {
    ETH_REQUEST Request;
    INTERMEDIATE_BUFFER PacketBuffer;
    }

    then store all packets for which decision is delayed into the memory and release the packet by retrieving the data from the structure as mentioned above.

    This way I am storing packet plus overhead. But if the packet data is stored somewhere else by winpkfilter framework, I will be duplicating data in memory. I rather use ID or ptr of some sort to identify the packet to release.

    I tried unsuccessfully to get info from forums.

    If I am asking the wrong question, my apologies. In such case, please direct me to correct url of such information.

    I believe that storing of packet information in the winpkfilter framework is unlikely as not releasing packet (as in passthru) is not informed back to the framework (like drop indication).

    Is there any information which I am missing completely?

    Thanks in advance.

    Anil Chandra K

    #6485

    Vadim Smirnov
    Moderator

    I believe that storing of packet information in the winpkfilter framework is unlikely as not releasing packet (as in passthru) is not informed back to the framework (like drop indication).

    You are right, WinpkFilter does not keep any references to the packet passed to you for the processing. In general your approach to making packet queues is ok.

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

You must be logged in to reply to this topic.