mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steve French <smfrench@gmail.com>
To: Jeremy Allison <jra@samba.org>
Cc: linux-cifs@vger.kernel.org,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Big performance improvements seen with cifs async write patches even over localhost
Date: Fri, 27 May 2011 12:09:30 -0500	[thread overview]
Message-ID: <BANLkTikCUy-R16_QhuwNtynP9mXd9zFDNQ@mail.gmail.com> (raw)
In-Reply-To: <20110527164702.GB28520@samba2>

On Fri, May 27, 2011 at 11:47 AM, Jeremy Allison <jra@samba.org> wrote:
> On Fri, May 27, 2011 at 12:14:19AM -0500, Steve French wrote:
>> Did some informal testing of Jeff Layton's cifs async_write patch set
>> tonight (recent kernel). Copying 700MB sequentially was 20% faster
>> from cifs kernel client to Samba 3.6 with his patches - even mounted
>> over localhost (where network latency is a much smaller issue) and
>> with a slow laptop drive!
>>
>> I was simply doing
>>
>> time dd if=/dev/zero of=/mnt/null bs=1M count=700
>>
>> repeated 4 times each way (with old module, and with same code with
>> Jeff's cifs async write code builtin), deleting the target file in
>> between each run.
>>
>> I am looking forward to trying this over GigE tomorrow to servers with
>> faster disks.

Note that Samba defaults to negotiating a 128K write size but sending
"min receivefile size" in smb.conf to a larger value will allow larger
writes.   I see slightly better performance on the simple dd test over
localhost network interface with larger wsize of 512K than I do with
the default (128K).   I haven't measured the ideal wsize yet but
presumably it will vary depending on network and disk speed and server
load.

> Very nice ! Now where's my encrypted transport Steve ? :-) :-)

First cleanup patch is in (which gracefully handles failing mounts
when server requires encryption and client can't do it).    The 2nd
part - the NTLMSSP negotiation inside setfsunixinfo wasn't too bad and
I plan to send out for review within a few days.  I haven't written
the piece which uses these credentials to do the encryption yet.



-- 
Thanks,

Steve

  reply	other threads:[~2011-05-27 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-27  5:14 Steve French
2011-05-27 16:47 ` Jeremy Allison
2011-05-27 17:09   ` Steve French [this message]
2011-05-28 17:21   ` 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=BANLkTikCUy-R16_QhuwNtynP9mXd9zFDNQ@mail.gmail.com \
    --to=smfrench@gmail.com \
    --cc=jra@samba.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.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

all inboxes | Powered by JetHome®