From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Steve French <smfrench@gmail.com>
Cc: Jeff Layton <jlayton@samba.org>,
"J. R. Okajima" <hooanon05@yahoo.co.jp>,
Jesper Juhl <jj@chaosbits.net>,
linux-kernel@vger.kernel.org, Alan Piszcz <ap@solarrain.com>,
Steve French <sfrench@samba.org>,
linux-cifs@vger.kernel.org
Subject: Re: Kernel 3.0: Instant kernel crash when mounting CIFS (also crashes with linux-3.1-rc2
Date: Thu, 18 Aug 2011 14:18:15 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1108181413030.7903@p34.internal.lan> (raw)
In-Reply-To: <CAH2r5msTpKdxwpgG+-3-gkkr5h7Ox1tL86q3LyTBMd1V8WS7aQ@mail.gmail.com>
On Thu, 18 Aug 2011, Steve French wrote:
> If reading files - smbclient (ftp like syntax) should be able to reach
> wire speeds (assuming the server disk can keep up) and for
> writing it should be similar (perhaps a little slower but it won't
> use i/o sizes as large as cifs kernel client). I would expect
> smbclient to/copy from Windows to be faster than Windows mount -> Samba.
>
> I reached near wirespeeds for GigE with cifs client (writing) to
> Winodws 2003/2008/r2
> and Samba - but didn't have fast enough disks to test 10GigE although I expect
> very good performance with that if you have fast enough server disks (and
> am willing to put performance patches in, if you detect additional
> changes that we should make for 10GigE - in particular allowing
> more than 50 simultaneous requests).
>
> If the registry fix for Windows 7 is in place (or if you copy to
> WIndows 2008, Windows 2003, WIndows 2008r2) -
> cifs kernel client is probably slightly faster for writes than alternatives,
> smbclient much faster for reads.
>
> If going the other direction (Windows client copying to/from Samba server) -
> Samba 3.6 (server) with SMB2 support
> turned on - is going to be faster than most alternatives.
Hi,
Downloading from an FTP Server on the windows machine:
<--- 150 Connection accepted
`file' at 418873344 (24%) 145.58M/s eta:9s [Receiving data]
`file' at 735510528 (42%) 162.93M/s eta:6s [Receiving data]
`file' at 1357185024 (78%) 172.89M/s eta:2s [Receiving data]
<--- 226 Transfer OK
---- Got EOF on data connection
---- Closing data socket
1719784995 bytes transferred in 9 seconds (181.65M/s)
Same file (via CIFS): 50MB/s
Device eth6 [10.0.1.2] (1/1):
================================================================================
Incoming: Outgoing:
Curr: 49.17 MByte/s Curr: 0.58 MByte/s
Avg: 8.76 MByte/s Avg: 0.03 MByte/s
Min: 0.00 MByte/s Min: 0.00 MByte/s
Max: 197.68 MByte/s Max: 0.86 MByte/s
Ttl: 585.87 GByte Ttl: 6.97 GByte
0.02user 4.09system 0:33.84elapsed 12%CPU (0avgtext+0avgdata 3632maxresident)k
The RAID's on both systems can achieve > 750MiB/s sustained without any
problems (benchmarked in the past) and the system has 56 PCI-e 2.0 lanes
and a cable between two 10GbE nics. Not sure where to start, Win7/box tweaks
or Linux/CIFS options?
Again, Samba -> Linux = 500MiB/s, so FTP > 3x faster than CIFS.
I know NFS gets a lot of testing (never had an issue with it/performance/etc)
However, regarding CIFS-- is there a test suite/or benchmark pack the CIFS
developers use to make sure everything is working in order?
Justin.
next prev parent reply other threads:[~2011-08-18 18:18 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 9:10 Kernel 3.0: Instant kernel crash when mounting CIFS Justin Piszcz
2011-08-15 9:18 ` Jesper Juhl
2011-08-15 10:47 ` Jeff Layton
2011-08-15 10:54 ` Justin Piszcz
2011-08-15 18:01 ` Justin Piszcz
2011-08-15 18:09 ` Steve French
2011-08-15 19:31 ` Dave Jones
2011-08-17 19:16 ` Kernel 3.0: Instant kernel crash when mounting CIFS (also crashes with linux-3.1-rc2 Justin Piszcz
[not found] ` <alpine.DEB.2.02.1108171545190.5877@p34.internal.lan>
2011-08-17 19:47 ` Justin Piszcz
2011-08-17 20:13 ` Jeff Layton
2011-08-17 20:45 ` Justin Piszcz
2011-08-17 21:11 ` Arnaud Lacombe
2011-08-17 21:53 ` Justin Piszcz
2011-08-17 22:13 ` Justin Piszcz
2011-08-17 22:18 ` Justin Piszcz
2011-08-17 23:31 ` Valdis.Kletnieks
2011-08-18 3:19 ` J. R. Okajima
2011-08-18 10:35 ` Justin Piszcz
2011-08-18 12:14 ` Justin Piszcz
2011-08-18 12:22 ` Justin Piszcz
2011-08-18 13:11 ` Jeff Layton
2011-08-18 13:15 ` Justin Piszcz
2011-08-18 17:04 ` Jeff Layton
2011-08-18 17:15 ` Steve French
2011-08-18 17:16 ` Justin Piszcz
2011-08-18 17:25 ` Steve French
2011-08-18 17:33 ` Justin Piszcz
2011-08-18 17:43 ` Steve French
2011-08-18 18:18 ` Justin Piszcz [this message]
2011-08-18 18:52 ` Jeff Layton
2011-08-18 18:54 ` Justin Piszcz
2011-08-18 19:02 ` Steve French
2011-08-26 21:59 ` Jeff Layton
2011-08-26 22:57 ` Justin Piszcz
2011-08-26 23:05 ` Steve French
2011-08-26 23:16 ` Justin Piszcz
2011-08-27 14:31 ` Jeff Layton
2011-08-18 17:36 ` Kong Li
2011-08-18 18:33 ` Jeff Layton
2011-08-18 14:19 ` J. R. Okajima
2011-08-18 16:01 ` Steve French
2011-08-18 16:02 ` 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=alpine.DEB.2.02.1108181413030.7903@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=ap@solarrain.com \
--cc=hooanon05@yahoo.co.jp \
--cc=jj@chaosbits.net \
--cc=jlayton@samba.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@samba.org \
--cc=smfrench@gmail.com \
/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
all inboxes | Powered by JetHome®