From: Ric Wheeler <rwheeler@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: "Greg Freemyer" <greg.freemyer@gmail.com>,
"Jörn Engel" <joern@logfs.org>,
"Matthew Wilcox" <willy@linux.intel.com>,
"Jens Axboe" <jens.axboe@oracle.com>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
"Linux RAID" <linux-raid@vger.kernel.org>
Subject: Re: Is TRIM/DISCARD going to be a performance problem?
Date: Mon, 11 May 2009 10:58:38 -0400 [thread overview]
Message-ID: <4A083D1E.2040807@redhat.com> (raw)
In-Reply-To: <20090511145059.GD6277@mit.edu>
On 05/11/2009 10:50 AM, Theodore Tso wrote:
> On Mon, May 11, 2009 at 10:29:51AM -0400, Ric Wheeler wrote:
>> The key is not at the FS layer - this is an issue for people who RAID
>> these beasts together and want to actually check that the bits are what
>> they should be (say doing a checksum validity check for a stripe).
>>
>
> Good point, yes I can see why they need that. In that case, the
> storage device can't just silently truncate a TRIM request; it would
> have to expose to the OS its alignment requirements. The risk though
> is that more they try push this compleixity into the OS, the higher
> the risk that the OS will simply decide not to take advantage of the
> functionality. Of course, there is the question why anyone would want
> to build a software-raid device on top of a thin-provisioned hardware
> storage unit. :-)
>
> - Ted
Probably not as uncommon as you would think, but not as you suggest to raid thin
provisioned luns (those are done usually as RAID devices inside an array).
Think more of the array providing a thinly provisioned LUN made up out of T13
TRIM enabled SSD's devices internally. RAID makes sense here (data protection
is still needed to avoid a single point of failure) and the relative expense of
the SSD's devices makes "thin provisioning" really attractive to external users :-)
ric
next prev parent reply other threads:[~2009-05-11 14:59 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-09 21:14 Is TRIM/DISCARD going to be a performance problem? Theodore Ts'o
2009-05-10 16:53 ` Jörn Engel
2009-05-11 8:37 ` Theodore Tso
2009-05-11 10:06 ` Jörn Engel
2009-05-11 10:18 ` Jens Axboe
2009-05-11 15:43 ` Jeff Garzik
2009-05-11 11:27 ` Theodore Tso
2009-05-11 12:09 ` Theodore Tso
2009-05-11 13:10 ` Greg Freemyer
2009-05-11 13:39 ` Matthew Wilcox
2009-05-11 14:27 ` Theodore Tso
2009-05-11 14:29 ` Ric Wheeler
2009-05-11 14:50 ` Theodore Tso
2009-05-11 14:58 ` Ric Wheeler [this message]
2009-05-11 15:00 ` Matthew Wilcox
2009-05-11 18:47 ` Greg Freemyer
2009-05-11 19:22 ` Andreas Dilger
2009-05-11 23:38 ` Neil Brown
2009-05-12 13:28 ` Greg Freemyer
2009-05-11 13:15 ` Ric Wheeler
2010-04-24 17:11 ` Phillip Susi
2009-05-11 12:43 ` Jörn Engel
2009-05-11 12:48 ` Matthew Wilcox
[not found] ` <f3177b9e0905111433i40e41c90r920d7ccf36442ffd@mail.gmail.com>
2009-05-11 22:03 ` Chris Worley
2009-05-11 16:30 ` Chris Worley
2009-05-11 8:12 ` Jens Axboe
2009-05-11 8:41 ` Theodore Tso
2009-05-11 8:49 ` Jens Axboe
2009-05-11 17:18 ` Chris Mason
2009-05-11 18:43 ` Matthew Wilcox
2009-05-11 18:53 ` Chris Mason
2009-05-11 19:19 ` Theodore Tso
2009-05-29 10:52 ` Florian Weimer
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=4A083D1E.2040807@redhat.com \
--to=rwheeler@redhat.com \
--cc=greg.freemyer@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=joern@logfs.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=willy@linux.intel.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;
as well as URLs for NNTP newsgroup(s).