On Tue, Dec 17, 2013 at 01:19:39AM +0000, Chris Mason wrote: > On Tue, 2013-12-17 at 02:06 +0100, David Sterba wrote: > > On Mon, Dec 16, 2013 at 01:26:26PM -0500, Josef Bacik wrote: > > > I need to create a fake tree to test qgroups and I don't want to have to setup a > > > fake btree_inode. The fact is we only use the radix tree for the fs_info, so > > > everybody else who allocates an extent_io_tree is just wasting the space anyway. > > > This patch moves the radix tree and its lock into btrfs_fs_info so there is less > > > stuff I have to fake to do qgroup sanity tests. Thanks, > > > > This would make the fs_info::buffer_lock a global hotspot if > > alloc_extent_buffer and release_extent_buffer are called frequently. > > > > But since the only place that was really using it was the metadata > btree, the lock shouldn't be hotter than before right? Right. What confused me first is that the number of trees that are initialized by extent_io_tree_init is higher, but the only user is metadata btree. -- 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
