so, instead of taking one (quite-well-tested) part that solves one of the biggest ext3 limitation, you propose to start a new project and get something in a year (probably) ? I think about extents as a step-by-step way ... thanks, Alex >>>>> Linus Torvalds (LT) writes: LT> Just as an example: ext3 _sucks_ in many ways. It has huge inodes that LT> take up way too much space in memory. It has absolutely disgusting code to LT> handle directory reading and writing (buffer heads! In 2006!). It's LT> conditional indexing code is horrible. Its performance absolutely sucks LT> when the journal is being drained or something. LT> Are you going to improve on any of those _fundamnetal_ problems? Or are LT> you going to make them worse? LT> Hint: I'm betting you're not going to improve them by adding more LT> features. - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
