summaryrefslogtreecommitdiffstats
path: root/fs/btrfs/free-space-cache.c
diff options
context:
space:
mode:
authorSage Weil2010-10-29 21:41:32 +0200
committerChris Mason2010-10-30 03:42:10 +0200
commit531cb13f1e417c060b54f979e1659ecd69bea650 (patch)
tree6b421ac1ddf7cad271cd0c767f0c19e6c4f826df /fs/btrfs/free-space-cache.c
parentBtrfs: add SNAP_CREATE_ASYNC ioctl (diff)
downloadkernel-qcow2-linux-531cb13f1e417c060b54f979e1659ecd69bea650.tar.gz
kernel-qcow2-linux-531cb13f1e417c060b54f979e1659ecd69bea650.tar.xz
kernel-qcow2-linux-531cb13f1e417c060b54f979e1659ecd69bea650.zip
Btrfs: make SNAP_DESTROY async
There is no reason to force an immediate commit when deleting a snapshot. Users have some expectation that space from a deleted snapshot be freed immediately, but even if we do commit the reclaim is a background process. If users _do_ want the deletion to be durable, they can call 'sync'. Signed-off-by: Sage Weil <sage@newdream.net> Signed-off-by: Chris Mason <chris.mason@oracle.com>
Diffstat (limited to 'fs/btrfs/free-space-cache.c')
0 files changed, 0 insertions, 0 deletions