linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: hdparm-9.17 released, with experimental trim/wiper scripts for SSDs
Date: Wed, 29 Jul 2009 19:35:20 -0400	[thread overview]
Message-ID: <4A70DCB8.9000909@rtr.ca> (raw)

hdparm-9.17 is now available from sourceforge.net.

New in this release:
        - added wiper/ subdirectory with preliminary SSD-wiper (TRIM) scripts
        - nuked kernel_patches/ subdirectory
        - Capitalize first word of each line of help output
        - added --fallocate flag
        - added --trim-sector-ranges flag
        - removed --trim-sectors flag
        - removed --fibmap-sector flag
        - embed VERSION string for easier digging out with strings(1)

This release is mostly in support of enabling user-initiated DSM/TRIM operations
for solid-state drives (SSDs).  The in-kernel support for automatic-TRIM seems
a ways off yet, so I'm providing scripts to do it auto/manually instead.  :)

These basically scan for free blocks in a filesystem, and batch them together
into huge DSM/TRIM commands to the drive, letting it know about them all for
garbage-collection and wear-leveling purposes.

These scripts are similar (but being Linux, superior) to an existing wiper.exe
utility that MS Win users have been enjoying for some brands of SSD.

But they won't actually do anything until drives ship with TRIM-enabled firmware.

Cheers 

             reply	other threads:[~2009-07-29 23:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29 23:35 Mark Lord [this message]
2009-07-29 23:39 ` hdparm-9.17 released, with experimental trim/wiper scripts for SSDs Mark Lord
2009-07-30  7:20   ` Robert Hancock
2009-07-30  8:24     ` Jeff Garzik
2009-07-30 12:54     ` Mark Lord
2009-07-30 18:27       ` Robert Hancock
2009-07-30 18:43         ` Mark Lord
2009-07-30 19:15           ` Mark Lord
2009-07-30 19:30         ` Mark Lord
2009-07-30 19:57           ` Robert Hancock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A70DCB8.9000909@rtr.ca \
    --to=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).