From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [PATCH 00/16] f2fs: introduce flash-friendly file system Date: Fri, 12 Oct 2012 20:55:02 +0000 Message-ID: <1715214.vxmSNGCbxl@wuerfel> References: <1349553966.12699.132.camel@kjgkr> <20121010045351.GE17429@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: =?utf-8?B?THVrw6HFoQ==?= Czerner , Jaegeuk Kim , 'Namjae Jeon' , 'Vyacheslav Dubeyko' , 'Marco Stornelli' , 'Jaegeuk Kim' , 'Al Viro' , gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, chur.lee@samsung.com, cm224.lee@samsung.com, jooyoung.hwang@samsung.com, linux-fsdevel@vger.kernel.org To: Theodore Ts'o Return-path: In-Reply-To: <20121010045351.GE17429@thunk.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wednesday 10 October 2012 00:53:51 Theodore Ts'o wrote: > On Tue, Oct 09, 2012 at 01:01:24PM +0200, Luk=C3=A1=C5=A1 Czerner wro= te: > > Do not get me wrong, I do not think it is worth to wait for vendors > > to come to their senses, but it is worth constantly reminding that > > we *need* this kind of information and those heuristics are not > > feasible in the long run anyway. >=20 > A number of us has been telling flash vendors exactly this. The > technical people do seem to understand. It's management who seem to > be primarily clueless, even though this information can be extracted > by employing timing attacks on the media. I've pointed this out > before, and the technical people agree that trying to keep this > information as a "trade secret" is pointless, stupid, and > counterproductive. Trying to get the pointy-haired bosses to > understand may take quite a while. =46or eMMC, I think we should start out defaulting to the characteristi= cs that are reported by the device, because they are usually correct and those vendors for which that is not true can hopefully come to their senses when they see how f2fs performs by default. =46or USB media, the protocol does not allow you to specify the erase block size, so we have to guess. =46or SD cards, there is a field in the card's registers, but I've never seen any value in there other than 4 MB, and in most cases where that is not true, the standard does not allow encoding the correct amount: it only allows power-of-two numbers up to 4 MB, and typical numbers these days are 3 MB, 6 MB or 8 MB. Arnd