From: Steve French <smfrench@austin.rr.com>
To: linux-cifs-client@lists.samba.org, linux-kernel@vger.kernel.org
Subject: cifs writepages patch
Date: Sun, 25 Sep 2005 16:17:01 -0500 [thread overview]
Message-ID: <433713CD.5050607@austin.rr.com> (raw)
I have been looking at and testing Shaggy's cifs writepages patches, and
they look promising.
From my fastest test client to a laptop running Windows XP as a test
server (unfortunately this means running against a relatively slow disk,
but the file size should fit in cache on the server) here are some
initial results (at least three runs at each size). Doing large file
copy (dd if=/dev/zero bs=16K count=4K of =/mnt/testfile) of 64Mbytes
Over 100Mbit Ethernet
w/o the patch (writes will go 4K): 6.1 MB/sec
w/patch and wsize 16K (default) 8.8MB/sec
w/patch and wsize reduced to 4K 6.3MB/sec
w/patch and wsize 8K 8.5 MB/sec
w/patch and wsize increased to 32K 9.8 MB/sec
next reply other threads:[~2005-09-25 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-25 21:17 Steve French [this message]
2005-09-26 2:35 ` cifs writepages patch Steve French
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=433713CD.5050607@austin.rr.com \
--to=smfrench@austin.rr.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox