diff options
author | Josef Bacik <josef@redhat.com> | 2011-06-28 16:18:59 -0400 |
---|---|---|
committer | Al Viro <viro@zeniv.linux.org.uk> | 2011-08-01 01:31:42 -0400 |
commit | b4aff1f874f679320c03e3d97b60fc7babfd4623 (patch) | |
tree | 7d70626056dd81bbdb194171d89f35cd390a5a78 /fs/utimes.c | |
parent | 9d108d25487bf958f8093409a4c0bee6169edba6 (diff) | |
download | linux-stable-b4aff1f874f679320c03e3d97b60fc7babfd4623.tar.gz linux-stable-b4aff1f874f679320c03e3d97b60fc7babfd4623.tar.bz2 linux-stable-b4aff1f874f679320c03e3d97b60fc7babfd4623.zip |
Btrfs: load the key from the dir item in readdir into a fake dentry
In btrfs we have 2 indexes for inodes. One is for readdir, it's in this nice
sequential order and works out brilliantly for readdir. However if you use ls,
it usually stat's each file it gets from readdir. This is where the second
index comes in, which is based on a hash of the name of the file. So then the
lookup has to lookup this index, and then lookup the inode. The index lookup is
going to be in random order (since its based on the name hash), which gives us
less than stellar performance. Since we know the inode location from the
readdir index, I create a dummy dentry and copy the location key into
dentry->d_fsdata. Then on lookup if we have d_fsdata we use that location to
lookup the inode, avoiding looking up the other directory index. Thanks,
Signed-off-by: Josef Bacik <josef@redhat.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs/utimes.c')
0 files changed, 0 insertions, 0 deletions