From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH] fat: make discard a mount option Date: Wed, 18 Nov 2009 20:15:11 +0100 Message-ID: <20091118191511.GA30512@lst.de> References: <20091118170841.GA25541@lst.de> <87d43f4r1v.fsf@devron.myhome.or.jp> <20091118185358.GA29399@lst.de> <87aayj1wg9.fsf@devron.myhome.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Christoph Hellwig , linux-fsdevel@vger.kernel.org To: OGAWA Hirofumi Return-path: Received: from verein.lst.de ([213.95.11.210]:37216 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932512AbZKRTPK (ORCPT ); Wed, 18 Nov 2009 14:15:10 -0500 Content-Disposition: inline In-Reply-To: <87aayj1wg9.fsf@devron.myhome.or.jp> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Nov 19, 2009 at 04:09:42AM +0900, OGAWA Hirofumi wrote: > Yes. But, on the other view, it is the capability of block device (trim > like stuff is useful on it, or not. Also it would be able to used for > blacklist from driver). Yes, and discard works perfectly fine on e.g. the OCZ Vertex SSDs or storage arrays. It's just not fast enough for the trim on transaction commit style support that was rushed into various filesystems. It works perfectly fine with Mark Lord's wiper.sh script, or with an updated version of my XFS btree walking periodic discard. > Well, actually, I'm caring the difference of default for those options > can confuse a bit for users. I think it should be off by default for everyone, and I'm trying to make sure that's the case everywhere.