diff options
author | Christoph Hellwig <hch@infradead.org> | 2008-08-13 06:18:07 (GMT) |
---|---|---|
committer | Lachlan McIlroy <lachlan@redback.melbourne.sgi.com> | 2008-08-13 06:18:07 (GMT) |
commit | e1cccd917be7364f81b5dc4e33ee3a6e0db21a99 (patch) | |
tree | 9722a113d77695d886e6d2c1bc504e98cdb97b67 /fs/xfs/xfs_itable.c | |
parent | 1550d0b0b08bc34c0c37a86bd884b1a70782104e (diff) | |
download | linux-e1cccd917be7364f81b5dc4e33ee3a6e0db21a99.tar.xz |
[XFS] kill xfs_lock_dir_and_entry
When multiple inodes are locked in XFS it happens in order of the inode
number, with the everything but the first inode trylocked if any of the
previous inodes is in the AIL.
Except for the sorting of the inodes this logic is implemented in
xfs_lock_inodes, but also partially duplicated in xfs_lock_dir_and_entry
in a particularly stupid way adds a lock roundtrip if the inode ordering
is not optimal.
This patch adds a new helper xfs_lock_two_inodes that takes two inodes and
locks them in the most optimal way according to the above locking protocol
and uses it for all places that want to lock two inodes.
The only caller of xfs_lock_inodes is xfs_rename which might lock up to
four inodes.
SGI-PV: 981498
SGI-Modid: xfs-linux-melb:xfs-kern:31772a
Signed-off-by: Christoph Hellwig <hch@infradead.org>
Signed-off-by: Donald Douwsma <donaldd@sgi.com>
Signed-off-by: Lachlan McIlroy <lachlan@sgi.com>
Diffstat (limited to 'fs/xfs/xfs_itable.c')
0 files changed, 0 insertions, 0 deletions