It is not documented since this is an internal facility of NDIS private to
that particular implementation.
What it is doing is private to NDIS and you should not rely on NDIS using
this thread or *a* thread for anything. NDIS specifies an async
request/completion model for just about everthing and both requests and
completions may occur in arbitrary contexts (except, of course,
NdisOpenAdapter() which you asked about in the other thread - its thread
context is not quite arbitrary).
From the stack trace I would guess (and this is a guess, I don’t know, I
didn’t write NDIS) that NDIS is using a worker thread to complete certain
NdisRequest()'s that have been made of miniports that for one reason or
another are in need of completion. For whatever reason, the stack
back-trace you grabbed suggests that the thread is in the middle of walking
the Miniport Open (list) for an adapter and getting a reference to one of
the open blocks.
A thread running in some other component is not a problem unless you know it
should not be running. Is this somehow causing a problem for you?
Good Luck,
Dave Cattley
Consulting Engineer
Systems Software Development
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@wipro.com
Sent: Monday, October 15, 2007 1:43 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] ndisMRundownRequests
Hi,
When Im debugging my Protocol Driver, in the Stacks I found some Ndis
created worker thread which is keep on running.Following is the stack
000080 85c02da8 0000001 RUNNING NDIS!ndisReferenceOpenByHandle+0x32
NDIS!ndisMRundownRequests+0x1c
NDIS!ndisWorkerThread+0x75
nt!PspSystemThreadStartup+0x34
nt!KiThreadStartup+0x16
I searched the DDK documentation to find what this thread is doing or which
part of my protocol driver caused Ndis to run this.Any help and suggestions
will be appreciated.
Thanks and Regards
Alex.
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer