diff options
author | Jeff Layton <jlayton@redhat.com> | 2012-05-01 21:41:49 (GMT) |
---|---|---|
committer | Steve French <sfrench@us.ibm.com> | 2012-05-02 03:27:54 (GMT) |
commit | 8f71465c19ffefbfd0da3c1f5dc172b4bce05e93 (patch) | |
tree | c27bb25b91b148e5977ea29132dc98ccea89f725 /fs/ramfs/file-nommu.c | |
parent | 156d17905e783d057061b3b56a9b3befec064e47 (diff) | |
download | linux-8f71465c19ffefbfd0da3c1f5dc172b4bce05e93.tar.xz |
cifs: don't cap ra_pages at the same level as default_backing_dev_info
While testing, I've found that even when we are able to negotiate a
much larger rsize with the server, on-the-wire reads often end up being
capped at 128k because of ra_pages being capped at that level.
Lifting this restriction gave almost a twofold increase in sequential
read performance on my craptactular KVM test rig with a 1M rsize.
I think this is safe since the actual ra_pages that the VM requests
is run through max_sane_readahead() prior to submitting the I/O. Under
memory pressure we should end up with large readahead requests being
suppressed anyway.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: Steve French <sfrench@us.ibm.com>
Diffstat (limited to 'fs/ramfs/file-nommu.c')
0 files changed, 0 insertions, 0 deletions