File spy output for memory mapped write.

Hi,

There is another test application that I have written that writes into the file using memory mapped api.

  1. Create file.
  2. Creating mapping to the file and map the view of the file.
  3. Write data
  4. Flush and then unmap view of the file.
  5. Close the file.

File spy output is below:

  1. Create file.
  2. FastIO query standard information done.
  3. Setinformation with paging i/o bit set.
  4. Read call with paging i/o bit set.
  5. Write call with paging i/o bit set.
  6. Cleanup call.

File size related questions:

  1. Here there is neither cached set information nor cached write. Where should I increase the file size and insert header?
  2. Also my previous approach [for applications not using memory mapped i/o] where I was inserting header in the paging write will fail as the two paging writes [for 1st test application and this test application] will have to be handled differently.

Thanks,
Trav