Revision 8f71465c19ffefbfd0da3c1f5dc172b4bce05e93 authored by Jeff Layton on 01 May 2012, 21:41:49 UTC, committed by Steve French on 02 May 2012, 03:27:54 UTC
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>
1 parent 156d179
locking-selftest-spin.h
#undef LOCK
#define LOCK L
#undef UNLOCK
#define UNLOCK U
#undef RLOCK
#undef WLOCK
#undef INIT
#define INIT SI
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...