Re: Getting drops on IM filter driver

One other thing that Stephan just reminded me of - it's entirely possible
that the system would be dropping packets with no IM whatsoever; have you
verified that the behavior doesn't occur with NO IM installed at all?

-Steve


On 5/27/06 5:43 PM, in article
1148769785.426890.10120@xxxxxxxxxxxxxxxxxxxxxxxxxxxx, "Stephan Wolf [MVP]"
<stewo68@xxxxxxxxxxx> wrote:

If it is actually the IM that is dropping packets, then what exactly is
the reason for it dropping packets? Probably because it has no more
free receive resources? This in turn means packets do not get handled
fast enough by whoever retrieves them from your IM. Since one usually
passes packets to some user-mode program, this means it is your
application that causes dropped packets, not the IM.

You should carefully analyze and measure the behaviour of your IM and
any associated applications. Use tools like those already mentioned by
Steve (e.g. VTune, see http://www.intel.com/vtune/, check the free
evaluation link there).

Also, try a uniporcessor system and also XP. Do these make any
difference?

Stephan
---
Gaurav wrote:
Hi,

I wrote a simple IM filter driver. This driver is working fine up to
800 mpbs for 1400 packet size. I am running this driver on a 4
processor machine. It start dropping the packing as and when i start
any application or even on a mouse movement.
Any one knows why this happen om a 4 processor machine(win 2003).

how can i minimize these drops.

One idea that came to my mind is to call KeRaiseIrql() at the start of
ProtocolReceive ()function and then again lower the IRQL at the end of
the function. This way atleast i wont get any interrupts on the
processor running IM driver.

Is therre any way to bind our driver to one processor.
Can we raise the interrupt priority of NIC.

Thanks in advance.

Gaurav


.

Relevant Pages

  • Re: Filter Hook
    ... the callback routine is been invoked at DISPATCH_LEVEL. ... If you really have to keep such a queue for the packets, then the IP filter driver is not suitable for your needs since you have to process all the packets in the callback routine without any wait actionand return it to the tcpip driver immediately when the callback routine returns. ... What IRQL are you running at when you crash, ...
    (microsoft.public.development.device.drivers)
  • Re: MAC bridging and sniffing packets with specific Ethertype
    ... That is, the Ethernet adapters are bound to the Mbridge driver (which, since ... Mbridge handles the bridging of packets between the adapters. ...
    (microsoft.public.windowsce.embedded)
  • Re: Degradation of TCP connection
    ... "Each of our boards will have an ethernet driver specific ... once you get a target into a failed state, ... when the VxWorks box stops ACKing packets sent from the Windows box. ...
    (comp.os.vxworks)
  • Re: Degradation of TCP connection
    ... and running ifconfigon the target does indeed show ... the huge number of dropped Rx packets, ... RX stall (possibly due to mishandled RX overrun in the driver) ... RX interrupts have stopped firing ...
    (comp.os.vxworks)
  • NDIS driver to modify IP headers
    ... certain multicast flows of data that are being sent by a Windows computer. ... I am using NuMega's DriverNetworks to create the driver and I am able to ... I know that I cannot modify NDIS packets that I did not allocate, ...
    (microsoft.public.development.device.drivers)