On Wed, 2008-08-06 at 16:36 -0400, jim owens wrote: > Chris Mason wrote: > > > Josef's allocator fix is on the list because we currently fall over in > > some workloads at 100% cpu time when the FS is 60% full. The space > > indexing is complex and strange, it just needs to be redone. > > I don't understand. Do you mean josef wants someone to fix > multithreading or do you mean he is doing that as part of > an allocator fix he is working on, or did you mean that > his work is an exception and you really were not looking at > doing any allocator changes? > Josef is fixing the way the allocator indexes free space in ram. This is different from working on the threading, but I'm holding off on the threading until after he is done. > I see this in your 0.16 list: > > > Better in-memory free space indexing (Josef) > > but did not tie it to the allocator. Is that it? > > and I'll add an area I missed before in the Development_timeline: > - Fallocate support (at least disk format level) > as part of the allocator bundle-of-too-much-work :) ;) fallocate would be important as well. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
