On Wed, Oct 21, 2009 at 05:41:36PM -0400, Josef Bacik wrote: > Hello, > > I've been thinking recently about how to fix the caching stuff so it isn't so > damned slow and had started to work on writing out the free space cache into > bitmaps for every dirty bitmap, but then Eric Sandeen pointed out that xfs > just > has a couple of btree's to track free space, so I started thinking about doing > it that way, since we do have this nice btree code laying about. > > There are a couple of problems with adding another free space root however:
The free space root seems like it will have a pretty high overhead to me. But, I do like your general idea of caching the free space map at commit time as an on-disk cache. I think as we nail down the enospc corners we can go back and give that a try. To get around the cow problem, we can log the cache to the log tree. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
