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

I have verified that it works for the case in which "min receivefile
size" is under 128K.  When I set it to 250000 and tried to read 148000
there were two or three problems (reply_write_and_X in Samba is
calling smb_len instead of smb_len_large and it is looking for
"req->unread_bytes" incorrectly in a few places in reply.c and
fileio.c

On Nov 2, 2007 6:43 PM, Jeremy Allison <jra@samba.org> wrote:
> 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.
>



-- 
Thanks,

Steve

      reply	other threads:[~2007-11-07 22:56 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 ` Large SMBwriteX testing Jeremy Allison
2007-11-07 22:56   ` Steve French [this message]

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=524f69650711071456l59186c44na837df5dbe340920@mail.gmail.com \
    --to=smfrench@gmail.com \
    --cc=aarora@linux.vnet.ibm.com \
    --cc=jra@samba.org \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=samba-technical@lists.samba.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;
as well as URLs for NNTP newsgroup(s).