Quote Originally Posted by overthere View Post
... using the SSDPerfAnalysis script along with the "x?" option (to request that the physical volume associated with the Logical Disk "x" be monitored rather than the associated physical device), I have re-confirmed (using a VMware virtual machine running Win7-x64 with virtual HDDs) that TRIM commands are seen by the hIOmon software as being successfully processed at the physical volume level within the operating system I/O stack.

I will continue to revisit this some more ...
To help dispel the notion/concern that the observation by hIOmon (see my post #189 above) that "Win 7 successfully issues TRIM commands to HDD-backed physical volumes" was somehow due to running within a virtual machine environment, yesterday evening I ran the hIOmon software upon a "native" Windows 7-x64 system (i.e., a laptop with a single HDD and only Win 7-64x installed) just to make sure nothing has changed (i.e., from prior testing by hyperI/O).

The results were the same: multiple "successful" TRIM commands observed at the physical volume level within the operating system I/O stack (but none at the physical device level).

This re-confirmed once again (as was first noticed well over a year ago ) that Windows 7 does successfully issue TRIM commands at the physical volume level even for a HDD.

The ability to discretely monitor I/O operations at the physical volume level (in addition to the physical device level) helps bring this nuance of TRIM within Win7 to light.