Btrfs: don't bother copying if we're only logging the inode
authorJosef Bacik <jbacik@fusionio.com>
Thu, 11 Oct 2012 20:17:34 +0000 (16:17 -0400)
committerChris Mason <chris.mason@fusionio.com>
Mon, 17 Dec 2012 01:46:22 +0000 (20:46 -0500)
commita95249b392c3ab843d7b25ab6817ecc9ea0b82ee
tree85489b441816bb50fb05f21057dd6e7a4374482b
parente99761514999f64aff1985460967f93d9e8417f4
Btrfs: don't bother copying if we're only logging the inode

We don't copy inode items anwyay, we just copy them straight into the log
from the in memory inode.  So if we know we're only logging the inode, don't
bother dropping anything, just try to insert it and either if it succeeds or
we get EEXIST we can update the inode item in the log and carry on.  Thanks,

Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
fs/btrfs/tree-log.c