Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S272165AbTHNFHE (ORCPT ); Thu, 14 Aug 2003 01:07:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S272166AbTHNFHE (ORCPT ); Thu, 14 Aug 2003 01:07:04 -0400 Received: from thebsh.namesys.com ([212.16.7.65]:58853 "HELO thebsh.namesys.com") by vger.kernel.org with SMTP id S272165AbTHNFHA (ORCPT ); Thu, 14 Aug 2003 01:07:00 -0400 Subject: Re: Reiser4 status: benchmarked vs. V3 (and ext3) From: Yury Umanets To: Bill Davidsen Cc: Daniel Egger , Hans Reiser , Nikita Danilov , Linux Kernel Mailinglist , reiserfs mailing list In-Reply-To: References: Content-Type: text/plain Organization: NAMESYS Message-Id: <1060837469.17622.6.camel@haron.namesys.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Thu, 14 Aug 2003 09:04:29 +0400 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1469 Lines: 39 On Thu, 2003-08-14 at 00:12, Bill Davidsen wrote: > On Sun, 27 Jul 2003, Yury Umanets wrote: > > > On Sun, 2003-07-27 at 18:10, Daniel Egger wrote: > > > Am Son, 2003-07-27 um 15.28 schrieb Hans Reiser: > > > > > or for which a wear leveling block device driver is used (I don't know > > > > if one exists for Linux). > > > > > > This is normally done by the filesystem (e.g. JFFS2). > > > > Normally device driver should be concerned about making wear out > > smaller. It is up to it IMHO. > > The driver should do the logical to physical mapping, but the portability > vanishes if the filesystem to physical mapping is not the same for all > machines and operating systems. For pluggable devices this is important. > > The leveling seems to be done by JFFs2 in a portable way, and that's as it > should be. If the leveling were in the driver I don't believe even FAT > would work. Hello Bill, Yes, you are right. Device driver cannot take care about leveling. It is able only to take care about simple caching (one erase block) in order to make wear out smaller and do not read/write whole block if one sector should be written. Part of a filesystem called "block allocator" should take care about leveling. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/