RE: NDIS DPC/ISR running in same thread in CE 5.0
- From: stjong@xxxxxxxxxxxxxxxxxxxx ("Soemin Tjong [MSFT]")
- Date: Wed, 29 Jun 2005 18:06:18 GMT
There is no mechanism to separate the threads calling MiniportISR( ) and
MiniportInterruptHandler( ), if your NIC buffers are really limited and you
must rely on system memory and a quick turn around, in CE you can spin a
thread to do the indication job. You'd want its priority to be near the
ISR priority (116) and if it's serialized miniport driver, it must call
NdisIMSwitchToMiniport( ) before it calls NDIS functions and
NdisIMRevertBack( ) afterwards.
Before you do that, another suggestion is to make sure that your
MiniportInterruptHandler( ) uses the more optimal
NdisMIndicateReceivePacket( ) and indicate as many packets as it can in one
indication compared to one packet at a time.
-- Soemin ---
Windows CE CoreOS/Networking
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- Follow-Ups:
- RE: NDIS DPC/ISR running in same thread in CE 5.0
- From: anonymous
- RE: NDIS DPC/ISR running in same thread in CE 5.0
- References:
- NDIS DPC/ISR running in same thread in CE 5.0
- From: anonymous
- NDIS DPC/ISR running in same thread in CE 5.0
- Prev by Date: Re: Partition NTFS
- Next by Date: RE: Is NdisMStartBufferPhysicalMapping a valid function in WinCE
- Previous by thread: NDIS DPC/ISR running in same thread in CE 5.0
- Next by thread: RE: NDIS DPC/ISR running in same thread in CE 5.0
- Index(es):