Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: David Disseldorp <ddiss@suse.de>
To: Steve French <smfrench@gmail.com>
Cc: "linux-cifs@vger.kernel.org" <linux-cifs@vger.kernel.org>,
	samba-technical <samba-technical@lists.samba.org>,
	David Disseldorp <ddiss@samba.org>
Subject: Re: New ioctl - FSCTL_DUPLICATE_EXTENTS_TO_FILE
Date: Wed, 28 Jan 2015 19:22:03 +0100	[thread overview]
Message-ID: <20150128192203.5dbb06ea@g21.suse.de> (raw)
In-Reply-To: <CAH2r5mu4zB08avnUSig5b-DGBekgOHVGoUYNNosOpvfAfOYBoA@mail.gmail.com>

On Tue, 27 Jan 2015 12:23:55 -0600, Steve French wrote:

> Has anyone tried the new ioctl (MS-FSCC) defined in the most recent
> update.  See section 2.3.7
> 
> Looks interesting for a new variant of copy offload
> 
> "A new File System Control (FSCTL) has been added to support the new
> FSCTL_DUPLICATE_EXTENTS_TO_FILE operation in [MS-FSA]."

I haven't played with it yet, but from the [MS-FCC] 20150119 preview
doc it looks very similar to copy-chunk, with a few small differences:
- It's only supported on ReFS, which may indicate that it's implemented
  using COW clones.
- It takes a regular file handle for the source, instead of requiring a
  preliminary SRV_REQUEST_RESUME_KEY exchange.
- Only a single chunk can be duplicated per request, rather than
  multiple.
- Overlapping ranges are not supported.
- The length field is 64-bits wide, instead of 32.
- The response only carries the status code. This may imply there is no
  server-advertised limit to the length of the request, further
  indicating that it's COW based.

Time to start poking around with smbtorture :)

Cheers, David

  reply	other threads:[~2015-01-28 18:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27 18:23 New ioctl Steve French
2015-01-28 18:22 ` David Disseldorp [this message]
     [not found]   ` <20150128192203.5dbb06ea-TzLh5lQYVSQb1SvskN2V4Q@public.gmane.org>
2015-02-09 23:51     ` New ioctl - FSCTL_DUPLICATE_EXTENTS_TO_FILE David Disseldorp
     [not found]       ` <20150210005120.6936991d-k1XZOR0ctBLN0uC3ymp8PA@public.gmane.org>
2015-02-10  7:14         ` Steve French
     [not found]           ` <CAH2r5mv4qnMAS4T38C1OB8sWi6MHqcD2i2zv7KbbtUYuGg=vOw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-10 21:35             ` Tom Talpey

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=20150128192203.5dbb06ea@g21.suse.de \
    --to=ddiss@suse.de \
    --cc=ddiss@samba.org \
    --cc=linux-cifs@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