Messages in this thread | ![/](/images/icornerl.gif) | | Date | Mon, 28 Jul 2003 17:29:38 +0400 | From | Hans Reiser <> | Subject | Re: Reiser4 status: benchmarked vs. V3 (and ext3) |
| |
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
- 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/
| ![\](/images/icornerr.gif) |