This is the fourth version of this set. The main changes since the 3rd set are: - it's been rebased on top of Steve's current master branch - testing showed that find_get_pages_tag would only return a maximum of 256 pages, which limited the wsize to 1M with 4k PAGE_CACHE_SIZE. So, the code now calls find_get_pages_tag multiple times until it gets all that it wants, it hits the end of the file, or no more dirty pages are present in the range. - the default wsize is now 1M, but it will negotiate downward depending on what the server supports. It can be set as high as ~16M, but some cursory testing didn't show any real improvement in throughput with a larger wsize than 1M (YMMV of course). - I dropped the patch to make the maxmpxcount be respected. I think that needs more careful consideration and is probably worthy of a separate patchset in its own right. At this point, I believe this set is ready for merge for 2.6.40. Once it goes in, I'll plan to spin up a patch to clarify the wsize= option in the mount.cifs manpage. Once this has had some soak time, I'll look at async readpages support as well, and maybe consider changing writepage to use an async call. Jeff Layton (7): cifs: consolidate SendReceive response checks cifs: make cifs_send_async take a kvec array cifs: don't call mid_q_entry->callback under the Global_MidLock cifs: add ignore_pend flag to cifs_call_async cifs: add cifs_async_writev cifs: convert cifs_writepages to use async writes cifs: clean up wsize negotiation and allow for larger wsize fs/cifs/cifsglob.h | 6 +- fs/cifs/cifsproto.h | 28 +++++- fs/cifs/cifssmb.c | 242 ++++++++++++++++++++++++++++++++++++++++++++++++++- fs/cifs/connect.c | 99 +++++++++++++++------ fs/cifs/file.c | 241 +++++++++++++++++++++------------------------------ fs/cifs/netmisc.c | 2 +- fs/cifs/transport.c | 196 ++++++++++++----------------------------- 7 files changed, 498 insertions(+), 316 deletions(-) -- 1.7.4.4 -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
