The most interesting thing I learned at Driver DevCon 2005 was...

Updated: June 10, 2005
On This Page
Peter Viscarola, OSR: ...How much the memory manager has changed/is changing for Windows Server 2003 SP1 and Windows Longhorn.Peter Viscarola, OSR: ...How much the memory manager has changed/is changing for Windows Server 2003 SP1 and Windows Longhorn.
Steve Dispensa, Positive Networks: ...that there was a long-standing bug in the Memory Manager that led to hard-to-trace crashes in certain filter drivers.Steve Dispensa, Positive Networks: ...that there was a long-standing bug in the Memory Manager that led to hard-to-trace crashes in certain filter drivers.

Peter Viscarola, OSR: ...How much the memory manager has changed/is changing for Windows Server 2003 SP1 and Windows Longhorn.

I was thrilled to hear that in Longhorn the memory manager would no longer limit its read/write requests to 64K, and (at least in current builds) will send individual I/O requests as big as 4GB (yup, that's 4 GIGAbytes). Also, I was really interested to learn that memory manager was using "dummy pages" to read in (and effectively discard) data from the backing store that might be older than that already in memory. This allows memory manager to create larger read operations than older versions allow.

Top of pageTop of page

Steve Dispensa, Positive Networks: ...that there was a long-standing bug in the Memory Manager that led to hard-to-trace crashes in certain filter drivers.

Landy Wang led an amazingly interesting session at which he discussed the issues that "dummy pages" raise. Read more here This link leaves the Microsoft.com site.


Top of pageTop of page