This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
The TRIM thread
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2009 03:11 PM
There's already a discussion on TRIM ( http://communities.intel.com/thread/5059?tstart=0 ), but the "Will the 34nm 25X-M drives be the only ones that will be able to be flashed for TRIM support?" question is not really the point of this thread.
Microsoft Windows 7 with TRIM support is already out there for MSDN subscribers like me (there's also a public Windows 7 RC), Linux kernel does support TRIM from version 2.6.28 and many users are waiting for TRIM support in order to buy an Intel SSD (G2).
So... what's the plan for a TRIM-capable firmware? Is there an ETA?
Thank you.
28 REPLIES 28
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2009 10:38 PM
Well, it already shipped, to MSDN at least.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2009 10:57 PM
"Shipped" would imply when it's for sale in stores. Non-public electronic distribution to places like Technet and MSDN isn't "shipped."
Many places are waiting for the actual public release date in October to put things out there, and just testing in the meantime.
All that having been said, the new firmware out in the last 24 hours might support things, but I can't seem to get my SSD recognized by the utility. I'll have to try it in another computer sometime.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2009 11:04 PM
Thank you for the English lesson.
Does anybody know the changes of this 1.3 firmware?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2009 11:38 PM
About 1.3 firmware...
"25 August 2009 045C8850 This firmware revision is for X25-E products only and has several continuous improvement optimizations intended to provide the best possible user experience with the Intel SSD"
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2009 05:44 PM
I'm interested in this as well.
Currently, when I download large files over an extended period of time I save them to a partition on my X25-M SSD, and when they are done they are automatically moved to my larger non-SSD HDD. I do this because then I can have a fairly quiet computer without the noise from the conventional HDD while downloading.However, I've started to worry that I may be degrading the performance of my SSD by doing this. I would very much like to have this cleared up; whether downloading large files to my SSD and moving them to some other HDD will actually cause a noticable performance degredation and if the TRIM command would be effective in preventing any supposed degredation.As I see it, when I write, for example, a 2GB file to my SSD and then move it to my large HDD, the SSD has no idea that I've moved the file, and the blocks that the Intel controller chose to write this file to are occupied even after moving the file. As my OS and file system probably doesn't know it's dealing with an SSD, it will just, when moving the file, note that the blocks on the SSD to which it thinks it wrote the 2GB file, are now free and can be overwritten, but not actually clear them. However, since this is an SSD my file system has no idea which blocks on the SSD the Intel controller chose to write this file to. So as I see it, the Intel controller will just keep filling up the SSD with these 2GB files looking for new empty blocks because it doesn't know that the blocks which were occupied by the previous 2GB file are not in use any more. How can this not degrade performance?
Related Content
