• J
    Btrfs: stop using GFP_ATOMIC for the tree mod log allocations · c8cc6341
    Josef Bacik 提交于
    Previously we held the tree mod lock when adding stuff because we use it to
    check and see if we truly do want to track tree modifications.  This is
    admirable, but GFP_ATOMIC in a critical area that is going to get hit pretty
    hard and often is not nice.  So instead do our basic checks to see if we don't
    need to track modifications, and if those pass then do our allocation, and then
    when we go to insert the new modification check if we still care, and if we
    don't just free up our mod and return.  Otherwise we're good to go and we can
    carry on.  Thanks,
    Signed-off-by: NJosef Bacik <jbacik@fusionio.com>
    Signed-off-by: NChris Mason <chris.mason@fusionio.com>
    c8cc6341
ctree.c 146.2 KB