Hi Slobodan,
You have just gotten to the same confusion I had
See below my last reply to you a while ago on the paging file problem. Now very informative but that was all I could get/guess that
time.
I am still unclear on how the paging is implemented. Why it bypasses EWF.
What I see is that RAM usage does not come up even if I have a lot of page faults (pagefile is used).
With a test app I consumed way more than Available physical memory, and Virtual/Pagefile memory was certainly used. However, I
was not observing the additional RAM usage coming from EWF. Therefore, I assumed paging was bypassing EWF.
Even if I had a small pagefile and after some allocations got "Low Memory.. adjusting the pagefile size.." system message and
the
pagefile was increased to the maximum specified, there was no EWF RAM usage increase.
I thought (guessed and some googling helped) that MM paging writes are implemented with calls to
IoSynchronousPageWrite(IRP_PAGING_IO). But then they definitely should end up calling to FS driver and then to EWF driver.
This is probably a question to comp.os.ms-windows.programmer.nt.kernel-mode. Or to whoever created EWF.
As I also mentioned in that thread
(
http://groups.google.com/groups?hl=...2MSFTNGP11.phx.gbl&rnum=1&prev=/groups?q=eXP+
paging%2Bgroup:microsoft.public.windowsxp.embedded.*%26hl%3Den%26lr%3D%26ie%3DUTF-8%26group%3Dmicrosoft.public.windowsxp.embedded.*%
26selm%3DeAMSOyMSEHA.1276%2540TK2MSFTNGP11.phx.gbl%26rnum%3D1) that EWF (enabled) RAM usage does not go up even if I see much of
paging in the system (used just to allocate big chunks of memory).
All this does not really help you but just FYI...
It would be really nice it you could clarify the issue

Good luck!
Regards,
Konstantin