From: Ric Wheeler <ricwheeler@gmail.com>
To: "Prof. Dr. Klaus Kusche" <klaus.kusche@computerix.info>
Cc: dgilbert@interlog.com, linux-scsi@vger.kernel.org,
Lukas Czerner <lczerner@redhat.com>, Mark Lord <mlord@pobox.com>
Subject: Re: Good SAS adapters for 6 Gb/s SATA SSD's (with TRIM)?
Date: Fri, 12 Aug 2011 10:35:05 +0100 [thread overview]
Message-ID: <4E44F3C9.4030708@gmail.com> (raw)
In-Reply-To: <4E44F14F.1020206@computerix.info>
On 08/12/2011 10:24 AM, Prof. Dr. Klaus Kusche wrote:
> On 2011-08-12 11:01, Ric Wheeler wrote:
>> Lukas has a more generic bulk tool that should do the job and has the
>> advantage that it does not have to fill the file system first (it can
>> lock regions and do its work).
>
> Any pointers to that?
I think that the easiest (and most natural way) to do this is through the
updated fsck (-K) tool which will discard the unused block ranges when you fsck
a file system.
Lukas can add in details about versions, etc :)
>
> Thanks!
>
>> Note that discard is not just for physical devices like SCSI or ATA, it
>> is also useful for "software" stacks like various device mapper targets,
>> virtual block devices, etc so we should be keeping the abstraction at a
>> high level for our tooling.
>
> I agree, but wiper.sh has been the first such tool and is widespread
> and well-known. I'm not aware of alternatives using the generic fstrim
> command (which is still missing on some major distributions)
> or FITRIM ioctl.
>
FITRIM is somewhat misnamed. It will end up issuing a discard to the storage
stack, not an ATA specific TRIM command (invoking sb_issue_discard()).
Anything that uses FITRIM should work if I followed the code correctly,
Ric
next prev parent reply other threads:[~2011-08-12 9:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 15:18 Good SAS adapters for 6 Gb/s SATA SSD's (with TRIM)? Prof. Dr. Klaus Kusche
2011-08-11 19:59 ` Douglas Gilbert
2011-08-12 3:19 ` Douglas Gilbert
2011-08-12 7:16 ` Stefan /*St0fF*/ Hübner
2011-08-12 13:42 ` Douglas Gilbert
2011-08-14 19:59 ` Stefan Hübner
2011-08-12 8:04 ` Prof. Dr. Klaus Kusche
2011-08-12 8:15 ` Ric Wheeler
2011-08-12 8:48 ` Prof. Dr. Klaus Kusche
2011-08-12 9:01 ` Ric Wheeler
2011-08-12 9:24 ` Prof. Dr. Klaus Kusche
2011-08-12 9:35 ` Ric Wheeler [this message]
2011-08-12 11:14 ` Lukas Czerner
2011-08-12 9:52 ` Lukas Czerner
2011-08-12 12:32 ` Mark Lord
2011-08-12 9:17 ` Artem Bokhan
2011-08-12 9:34 ` Artem Bokhan
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=4E44F3C9.4030708@gmail.com \
--to=ricwheeler@gmail.com \
--cc=dgilbert@interlog.com \
--cc=klaus.kusche@computerix.info \
--cc=lczerner@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mlord@pobox.com \
/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