tree d303bffbd895c307f49286cd90186cf58223dde2
parent 589d8ade83f07c0f11c8191c0ca309f34d7a2c14
author Josef Bacik <josef@redhat.com> 1305297131 -0400
committer Josef Bacik <josef@redhat.com> 1306170194 -0400

Btrfs: don't always do readahead

Our readahead is sort of sloppy, and really isn't always needed.  For example if
ls is doing a stating ls (which is the default) it's going to stat in non-disk
order, so if say you have a directory with a stupid amount of files, readahead
is going to do nothing but waste time in the case of doing the stat.  Taking the
unconditional readahead out made my test go from 57 minutes to 36 minutes.  This
means that everywhere we do loop through the tree we want to make sure we do set
path->reada properly, so I went through and found all of the places where we
loop through the path and set reada to 1.  Thanks,

Signed-off-by: Josef Bacik <josef@redhat.com>