Re: High DPC Use and a Method to Reboot a network card?

Are you saying you are sending 2^32 = ~4 billion *packets*, or are you
talking about the amount of *data* sent?

In either case, the amount of packets and/or data sent should of course
never cause such (or any other) problems.

Now what do you mean by "the NIC or WinPCap [..] becomes unstable"? I
don't think any protocol driver has a DPR, so it's most likely the
NIC's *driver* (not the NIC itself) that keeps spending time in DPCs.

In any event, you should try to get an updated driver.

A NIC driver cannot "reboot", but you can unload and reload it either
manually in the network configuration dialogue or in device manager or
by using SetupDi functions. For the latter see the DevCon sample source
code in the DDK.

Stephan
---
IMH wrote:
Hi All

I am using a 3COM 3C2000 NIC to capture MPEG from proprietry hardware.
After we have sent the NIC 2^32 packets of data the NIC or WinPCap which we
are using to perform the capture becomes unstable, spending 50% of the CPU
time servicing DPCs. This is very bad as on some machines these DPCs all
schedule on the same processor (it's a hyperthreaded box) and this makes the
machine unusable.

I was hoping to be able to reboot the NIC in case that is the thing at fault
but thus far I've had no success and cannot find anyt IOCTL commands that
might achieve this for me.

Can anyone help or advise on a newsgroup more appropriate for this subject?

Thanks a lot
Cheers

.

Relevant Pages

  • Re: High DPC Use and a Method to Reboot a network card?
    ... We are sending UDP packets with a payload of 1028 bytes but I am talking ... In which case this almost certainly appears to be driver ... to reboot it; clearly it's a little more complicated than that however. ... NIC's *driver* that keeps spending time in DPCs. ...
    (microsoft.public.development.device.drivers)
  • 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: Test on 10GBE Intel based network card
    ... Who ya gonna call, why me of course, its my driver:) ... ix0: ... Driver dropped packets = 0 ... ix1: ...
    (freebsd-performance)
  • 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)