The number one (to my mind) is the additional support for 16TB address
spaces. There are also even more driver verifier checks, many of which are
embedded within VM. The limits of pool have changed again. The page
recycling algorithms have changed again. Note that these are not
*fundamental* changes (architectural) but still hit people.
Here’s an interesting one that I heard someone ran into recently - in
earlier versions VirtualProtect could be used to change the protection on
pages that XP and .NET will deny. In the specific case I saw, someone had
memory mapped a file read-only, used VirtualProtect to make the page
writeable, updated the page, and then changed the protection BACK to
read-only. Works fine in Windows 2000. Fails in XP and .NET.
It keeps things interesting. And ensures we’ll all have plenty to do in the
future as well!
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
See the new NTFSD FAQ on the OSR Web Site!
-----Original Message-----
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Sent: Wednesday, January 02, 2002 2:15 PM
To: File Systems Developers
Subject: [ntfsd] RE: [OT] When does the Working set manager invalidate s PT
E’s to share d pages?
Did I mention that VM is complicated? And getting more complicated with
each
new OS release!
And what are the serious differences in VM from NT3 to XP except the
xxxSpecifyCache functions and caching bits check in XP?
Max
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com