On Mon, 2013-12-16 at 15:25 +0800, Liu Bo wrote: > Inode cache is similar to free space cache and in fact shares the same > code, however, we don't load inode cache unless we're about to allocate > inode id, then there is a case where we only commit the transaction during > other operations, such as snapshot creation, we now update fs roots' generation > to the new transaction id, after that when we want to load the inode cache, > we'll find that it's not valid thanks to the mismatch of generation, and we > have to push btrfs-ino-cache thread to build inode cache from disk, and > this operation is sometimes time-costing. > > So to fix the above, we load inode cache into memory during reading fs root. Please reorder these so the patch that causes problems comes after the patches that fix the problems ;) IOW, please make it bisect friendly. -chris {.n++%ݶw{.n+{k~^nrzh&zzޗ++zfh~iz_j:+v)ߣm