diff options
author | Chris Mason <chris.mason@oracle.com> | 2009-09-02 15:04:12 -0400 |
---|---|---|
committer | Chris Mason <chris.mason@oracle.com> | 2009-09-11 13:31:06 -0400 |
commit | 2c64c53d8d30d43d0670482503a3914dfd3d6d46 (patch) | |
tree | cfe7bfa8f5dc4078f8c995f305229622e25572b1 /fs/coda | |
parent | 1edbb734b4e010974c41d2859d22a43d04f5f1cf (diff) |
Btrfs: cache values for locking extents
Many of the btrfs extent state tree users follow the same pattern.
They lock an extent range in the tree, do some operation and then
unlock.
This translates to at least 2 rbtree searches, and maybe more if they
are doing operations on the extent state tree. A locked extent
in the tree isn't going to be merged or changed, and so we can
safely return the extent state structure as a cached handle.
This changes set_extent_bit to give back a cached handle, and also
changes both set_extent_bit and clear_extent_bit to use the cached
handle if it is available.
Signed-off-by: Chris Mason <chris.mason@oracle.com>
Diffstat (limited to 'fs/coda')
0 files changed, 0 insertions, 0 deletions