diff options
| author | Chris Mason <chris.mason@oracle.com> | 2010-02-03 18:18:45 +0000 |
|---|---|---|
| committer | Chris Mason <chris.mason@oracle.com> | 2010-03-15 11:00:12 -0400 |
| commit | 4125bf761cd0786e1163e024c7c809ce2cc625bc (patch) | |
| tree | 3e1b73b0db29994e8fb56c727c38c1167922f189 /fs/btrfs/ordered-data.c | |
| parent | 0be2e98173f8badd5ccc7c2e994891746ba1caf4 (diff) | |
| download | kernel_samsung_smdk4412-4125bf761cd0786e1163e024c7c809ce2cc625bc.zip kernel_samsung_smdk4412-4125bf761cd0786e1163e024c7c809ce2cc625bc.tar.gz kernel_samsung_smdk4412-4125bf761cd0786e1163e024c7c809ce2cc625bc.tar.bz2 | |
Btrfs: finish read pages in the order they are submitted
The endio is done at reverse order of bio vectors.
That means for a sequential read, the page first submitted will finish
last in a bio. Considering we will do checksum (making cache hot) for
every page, this does introduce delay (and chance to squeeze cache used
soon) for pages submitted at the begining.
I don't observe obvious performance difference with below patch at my
simple test, but seems more natural to finish read in the order they are
submitted.
Signed-off-by: Shaohua Li <shaohua.li@intel.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
Diffstat (limited to 'fs/btrfs/ordered-data.c')
0 files changed, 0 insertions, 0 deletions