Prev: memory descriptor list
Next: memory descriptor list
From: codeFather on 11 Jun 2010 11:13
thanks for the post.
so this is how a MDL helps a DMA driver? it does the virtual to physical
address translation and stores the physical addresses associated with each
virtual page at the tail of the MDL structure? so if next time i access a
particular virtual page via MDL.mappedSystemVa instead of translating the
virtual address it just returns the value in the array at the tail of the MDL
(which supposedly contains the physical address that VA maps to) ? if yes,
then what is the function of the MmMapLockedPages?

thanks again!


From: Scott Noone on 11 Jun 2010 11:57
You're confusing two separate things that the MDL does. Try starting here
and see if this clears anything up:

http://www.osronline.com/article.cfm?id=423

-scott

--
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com


"codeFather" <codeFather(a)discussions.microsoft.com> wrote in message
news:4E33B5F9-AF4C-495D-96E4-8E6CD4A6FCCD(a)microsoft.com...
> thanks for the post.
> so this is how a MDL helps a DMA driver? it does the virtual to physical
> address translation and stores the physical addresses associated with each
> virtual page at the tail of the MDL structure? so if next time i access a
> particular virtual page via MDL.mappedSystemVa instead of translating the
> virtual address it just returns the value in the array at the tail of the
> MDL
> (which supposedly contains the physical address that VA maps to) ? if yes,
> then what is the function of the MmMapLockedPages?
>
> thanks again!
>
>
 | 
Pages: 1
Prev: memory descriptor list
Next: memory descriptor list