Read more.Microsoft has provided a Q&A for solid state drives in Windows 7, detailing a number of OS-specific enhancements.
Read more.Microsoft has provided a Q&A for solid state drives in Windows 7, detailing a number of OS-specific enhancements.
Interesting info in the comments under the blog about SSD RAIDs.
Seems the SSD features will work if you RAID controller tells the OS it's disk are zero speed.....now I am going to have to do some digging to find out where to check that
Main PC: Asus Rampage IV Extreme / 3960X@4.5GHz / Antec H1200 Pro / 32GB DDR3-1866 Quad Channel / Sapphire Fury X / Areca 1680 / 850W EVGA SuperNOVA Gold 2 / Corsair 600T / 2x Dell 3007 / 4 x 250GB SSD + 2 x 80GB SSD / 4 x 1TB HDD (RAID 10) / Windows 10 Pro, Yosemite & Ubuntu
HTPC: AsRock Z77 Pro 4 / 3770K@4.2GHz / 24GB / GTX 1080 / SST-LC20 / Antec TP-550 / Hisense 65k5510 4K TV / HTC Vive / 2 x 240GB SSD + 12TB HDD Space / Race Seat / Logitech G29 / Win 10 Pro
HTPC2: Asus AM1I-A / 5150 / 4GB / Corsair Force 3 240GB / Silverstone SST-ML05B + ST30SF / Samsung UE60H6200 TV / Windows 10 Pro
Spare/Loaner: Gigabyte EX58-UD5 / i950 / 12GB / HD7870 / Corsair 300R / Silverpower 700W modular
NAS 1: HP N40L / 12GB ECC RAM / 2 x 3TB Arrays || NAS 2: Dell PowerEdge T110 II / 24GB ECC RAM / 2 x 3TB Hybrid arrays || Network:Buffalo WZR-1166DHP w/DD-WRT + HP ProCurve 1800-24G
Laptop: Dell Precision 5510 Printer: HP CP1515n || Phone: Huawei P30 || Other: Samsung Galaxy Tab 4 Pro 10.1 CM14 / Playstation 4 + G29 + 2TB Hybrid drive
I still don't understand why an Operating System needs to be aware that much of the underlying disk structure.
An SSD's controller should make it behave in an appropriate way, and hide the rest of the goings on.
The OS isn't enhancing the drive, its optimising itself to perform better with an SSD.
There are certain features in the OS that become obsolete with an SSD due to its very fast access, things like Indexing which helps speed up searches, implemented because of how sluggish spindle drives can be in that respect.
How does the RAID controller even tell whether a drive is a disk or SSD, much less pass on that information to Windows?
I could be wrong, but as far as I know, only the firmware on the drive itself is aware of what type it is. The only thing the RAID controller and/or OS knows is that it's a "SATA device".
Am I right or wrong?
wouldn't think the raid controller needed to do any of that, i mean, it knows the physical makeup of the drive but i wouldn't have thought it had to act on it in any way... as long as the OS knows its all good?
VodkaOriginally Posted by Ephesians
SSD's are detected by reporting a rotational speed of 0, if the RAID controller passes this information along to Windows 7 the drives will be treated as SSD drives by Windows. So I guess it depends on the RAID card being used and the information provided to Windows by the card.
If the RAID card's have problems with not sending this information Microsoft should allow some configuration option to set the drives as SSD devices but they don't really go into detail on the subject.
So maybe you could have the trim command sent to all your drives, SSD or not, and if not supported they will just ignore it.Originally Posted by Microsoft Blog
Interesting blog post, I'm suprised to read that TRIM was supported in the beta of Windows 7 aswell as the RC, I thought it would be added with the retail release or maybe even in SP1. Keeping the page file on the SSD being recommended is also a suprise, I have my page file disabled anyway.
It'll be interesting to see how long it takes manufacturers to enable support for the command and which manufacturers don't bother adding support or try to get their customers to upgrade to a newer drive.
I was refering to moving the page file over to another HDD if you have one to reduce wear, which is what most SSD manufacturers recommend. While disabling the page file isn't recommended I've had no problems with it disabled and have been running my PC this way for over a year.
There is actually a fair bit of information passed between the disk and controller. At the heart of this you have CHS information (Cylinders, Heads and Sectors). In the old days you'd have to set this manually, and doing it wrong could mean anything from non working hardware, to corruption.
This doesn't even take into account that the controller could just read the drive firmware directly if it really wanted to (although this is long winded and rather pointless - it can be done).
There are also a number of other technologies that expose themselves to the controller like NCQ. If the drive didn't pass this information to the controller, they wouldn't work.
These days things like CHS information is done without the user ever seeing it. You plug the driver in, and it works.
So as far as the firmware only knowing what the disk really is - hell no, the controller and the disk pass a lot more information than you realise. If the controller uses this though purely depends on the device
And the OS can of course override all this and take complete control and do everything itself.
When disks moved to 48bit addressing to get over the 137GB limit of 32bit addressing, you needed a controller that knew about 48bit addressing..... or just just a new Linux kernel that could deal with it all itself regardless of what the BIOS or controller thought it was doing
There are currently 1 users browsing this thread. (0 members and 1 guests)