RE: NDIS DPC/ISR running in same thread in CE 5.0
- From: anonymous <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 30 Jun 2005 06:59:02 -0700
Thanks. That appears to address my issue.
One follow-on question. Previously, MiniportISR ran at 116,
MiniportHandlerInterrupt ran at 118, and other threads were either at 118 or
lower (or at the caller's priority).
If I set MiniportISR/MiniportHandlerInterrupt to run at 116, and my
indication thread at 118, are there other threads at 116 or 117 involved with
NDIS that I need to be concerned about locking up ?
""Soemin Tjong [MSFT]"" wrote:
> 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.
>
>
.
- References:
- 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
- From: "Soemin Tjong [MSFT]"
- NDIS DPC/ISR running in same thread in CE 5.0
- Prev by Date: How I download kernel on parallel port?
- Next by Date: how can I use the D-link 530 card to link platbuilder?
- Previous by thread: RE: NDIS DPC/ISR running in same thread in CE 5.0
- Next by thread: CEC vs. project
- Index(es):
Relevant Pages
|
|
