From: Mark Lord Subject: Re: [PATCH 1/2] fs: Do not dispatch FITRIM through separate super_operation Date: Fri, 19 Nov 2010 17:49:58 -0500 Message-ID: <4CE6FF16.90701__22895.487471442$1290207043$gmane$org@teksavvy.com> References: <20101118134804.GN5618@dhcp231-156.rdu.redhat.com> <20101118141957.GK6178@parisc-linux.org> <20101118142918.GA18510@infradead.org> <1290100750.3041.72.camel@mulgrave.site> <1290168976.2570.45.camel@dolmen> <4CE68155.50705@teksavvy.com> <20101119140203.GC10039@thunk.org> <4CE69940.6040908@teksavvy.com> <20101119163013.GJ10039@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit To: Ted Ts'o , Lukas Czerner , Steven Whitehouse , James Bottomley , Christoph Hellwig Received: from ironport2-out.teksavvy.com ([206.248.154.183]:32302 "EHLO ironport2-out.pppoe.ca" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1757181Ab0KSWuC (ORCPT ); Fri, 19 Nov 2010 17:50:02 -0500 In-Reply-To: <20101119163013.GJ10039@thunk.org> Sender: linux-ext4-owner@vger.kernel.org List-ID: On 10-11-19 11:30 AM, Ted Ts'o wrote: > > If there are some incompetently implemented SSD's out there which do a > flash erase of the entire SSD upon receiving a TRIM command (new > flash! Part of the whole *point* of a TRIM was to increase write > endurance by eliminating the need to copy blocks that really weren't > in use any more by the OS when the SSD is doing a GC copy/compaction > of a partially written flash sector), all I can do is do a sigh, and > wish that T13 had defined a "comptently implemented SSD bit" --- not > that Indilinix would admit if it they were incompetent. :-/ The Sandforce drives seem even slower for mke2fs than the Indilinx. And both types are faster than the Intel units for desktop use. At least they optimized for the important commands. :) Cheers