summaryrefslogtreecommitdiffstats
path: root/sound
diff options
context:
space:
mode:
authorJeff Layton <jlayton@redhat.com>2012-05-01 17:41:49 -0400
committerSteve French <sfrench@us.ibm.com>2012-05-01 22:27:54 -0500
commit8f71465c19ffefbfd0da3c1f5dc172b4bce05e93 (patch)
treec27bb25b91b148e5977ea29132dc98ccea89f725 /sound
parent156d17905e783d057061b3b56a9b3befec064e47 (diff)
downloadlinux-8f71465c19ffefbfd0da3c1f5dc172b4bce05e93.tar.gz
linux-8f71465c19ffefbfd0da3c1f5dc172b4bce05e93.tar.bz2
linux-8f71465c19ffefbfd0da3c1f5dc172b4bce05e93.zip
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 'sound')
0 files changed, 0 insertions, 0 deletions