From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Mason Subject: Re: thin provisioned LUN support Date: Fri, 07 Nov 2008 10:49:30 -0500 Message-ID: <1226072970.15281.46.camel@think.oraclecorp.com> References: <4913028B.6010405@redhat.com> <1225984628.4703.80.camel@localhost.localdomain> <20081107120534.GO21867@kernel.dk> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: David Woodhouse , James Bottomley , Ric Wheeler , linux-scsi@vger.kernel.org, linux-fsdevel@vger.kernel.org, Black_David@emc.com, "Martin K. Petersen" , Tom Coughlan , Matthew Wilcox To: Jens Axboe Return-path: Received: from rcsinet11.oracle.com ([148.87.113.123]:63010 "EHLO rgminet11.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751311AbYKGPu3 (ORCPT ); Fri, 7 Nov 2008 10:50:29 -0500 In-Reply-To: <20081107120534.GO21867@kernel.dk> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, 2008-11-07 at 13:05 +0100, Jens Axboe wrote: > > >I skimmed it but don't see any update implying that trim might be > > >ineffective if we align wrongly ... where is this? > > > > I think we should be content to declare such devices 'broken'. > > > > They have to keep track of individual sectors _anyway_, and dropping > > information for small discard requests is just careless. > > I agree, seems pretty pointless. Lets let evolution take care of this > issue. I have to say I'm surprised that it really IS an issue to begin > with, are array firmwares really that silly? > > It's not that it would be hard to support (and it would eliminate the > need to do discard merging in the block layer), but it seems like one of > those things that will be of little use in even in the near future. > Discard merging should be useful, I have no problem merging something > like that. > Hmmm, it's surprising to me that arrays who tell us please use the noop elevator suddenly want us to merge discard requests. The array really needs to be able to deal with this internally. Not that discard merging is bad, but I agree that we need to push this problem off on the array vendors. -chris