From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hans Reiser Subject: Re: Reiser4 status: benchmarked vs. V3 (and ext3) Date: Mon, 28 Jul 2003 17:29:38 +0400 Message-ID: <3F252542.3050703@namesys.com> References: <3F1EF7DB.2010805@namesys.com> <1059062380.29238.260.camel@sonja> <16160.4704.102110.352311@laputa.namesys.com> <1059093594.29239.314.camel@sonja> <16161.10863.793737.229170@laputa.namesys.com> <1059142851.6962.18.camel@sonja> <3F23CCBC.9070600@namesys.com> <1059315409.10692.215.camel@sonja> <3F251A97.9010409@namesys.com> <1059397619.31053.27.camel@sonja> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <1059397619.31053.27.camel@sonja> List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Daniel Egger Cc: Nikita Danilov , Linux Kernel Mailinglist , reiserfs mailing list Daniel Egger wrote: >Am Mon, 2003-07-28 um 14.44 schrieb Hans Reiser: > > > >>>This looks fine for normal harddrives put on flash you'd probably like >>>to write the data evenly over the free space in some already formatted >>>section still leaving the oportunity to format some other sectors to not >>>run out of space. >>> >>> > > > >>I was not able to parse the sentence above.;-) >> >> > >s/put/but/ > >As already mentioned the flash chips have to be erased before they can >be written. The erasesize is much larger than the typical block size >which means that although a block doesn't contain valid data it still >contains something which means that it cannot be written until it was >erased. That's why JFFS2 is using garbage collection to reclaim unused >but (at the moment) unusable space. > > > >>No, you could be more clever than that. >> >> > >Sure. :) > > > If you feel ambitious, try increasing the reiser4 node size to equal the erase size. This requires changes to VM though. -- Hans