linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Allison <jra@samba.org>
To: Steve French <smfrench@gmail.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-cifs-client@lists.samba.org,
	"Amit K. Arora" <aarora@linux.vnet.ibm.com>,
	samba-technical@lists.samba.org
Subject: Large SMBwriteX testing.
Date: Fri, 2 Nov 2007 17:43:12 -0700	[thread overview]
Message-ID: <20071103004312.GA1204@samba1> (raw)
In-Reply-To: <524f69650711011216s17cbc26ra337d70a0bde8d03@mail.gmail.com>

Hi Steve,

	I've finished adding the ability for smbd to support up to
16MB writeX calls in the latest git 3.2 tree.

To enable, set the parameter :

min receivefile size = XXX

where XXX is the smallest writeX you want to handle with recvfile.

The linux kernel doesn't yet support zerocopy from network to
file (ie. splice only works one way currently) so it's emulated
in userspace (with a 128k staging buffer) for now.

Also it must be an unsigned connection (for obvious reasons).

Once you've set this param smbd will start reporting
CIFS_UNIX_LARGE_WRITE_CAP on a SMB_QUERY_CIFS_UNIX_INFO:
call and you should be good to go. You'll need to use
a writeX call identical to Windows (14 wct with a 1 byte
pad field) in order to trigger the new code.

Let me know if you get the chance to test it and if
it makes a speed difference for CIFSFS.

Cheers,

	Jeremy.

  parent reply	other threads:[~2007-11-03  0:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-01 19:16 punching holes in files Steve French
2007-11-01 23:17 ` Anton Altaparmakov
2007-11-02  7:30   ` Volker Lendecke
2007-11-03  0:43 ` Jeremy Allison [this message]
2007-11-07 22:56   ` Large SMBwriteX testing 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=20071103004312.GA1204@samba1 \
    --to=jra@samba.org \
    --cc=aarora@linux.vnet.ibm.com \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=samba-technical@lists.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;
as well as URLs for NNTP newsgroup(s).