From: Christoph Hellwig Subject: Re: [PATCH 1/2] fs: Do not dispatch FITRIM through separate super_operation Date: Fri, 19 Nov 2010 11:38:28 -0500 Message-ID: <20101119163828.GA8023@infradead.org> References: <1290100750.3041.72.camel@mulgrave.site> <1290102098.3041.77.camel@mulgrave.site> <4CE59E57.2090009@teksavvy.com> <4CE5C616.7070706@teksavvy.com> <20101119115516.GA1152@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Christoph Hellwig , Mark Lord , "Martin K. Petersen" , James Bottomley , Jeff Moyer , Matthew Wilcox , Josef Bacik , Lukas Czerner , tytso@mit.edu, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, sandeen@redhat.com To: Greg Freemyer Return-path: Received: from bombadil.infradead.org ([18.85.46.34]:49521 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753190Ab0KSQiq (ORCPT ); Fri, 19 Nov 2010 11:38:46 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-ext4-owner@vger.kernel.org List-ID: On Fri, Nov 19, 2010 at 08:20:58AM -0800, Greg Freemyer wrote: > The kernel team has been coding around some Utopian SSD TRIM > implementation for at least 2 years with the basic assumption that > SSDs can handle thousands of trims per second. Just mix em in with > the rest of the i/o. No problem. Intel swore to us its the right > thing to do. Thanks Greg, good that you told us what we've been doing. I would have forgot myself if you didn't remember me. > I'm still waiting to see the first benchmark report from anywhere > (SSD, Thin Provisioned SCSI) that the online approach used by mount -o > discard is a win performance wise. Linux has a history of designing > for reality, but for some reason when it comes to SSDs reality seems > not to be a big concern. Both Lukas and I have done extensive benchmarks on various SSDs and thinkly provisioned raids. Unfortunately most of the hardware is only available under NDA so we can't publish it. For the XFS side which I've looked it I can summarize that we do have arrays that do the online discard without measureable performance penalty on various workloads, and we have devices (both SSDs and arrays) where the overhead is incredibly huge. I can also say that doing the walk of the freespace btrees similar to the offline discard, but every 30 seconds or at a similarly high interval is a sure way to completely kill performance. Or in short we haven't fund the holy grail yet.