All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	Ric Wheeler <ricwheeler@gmail.com>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Hannes Reinecke <hare@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-nfs@vger.kernel.org, Joel Becker <jlbec@evilplan.org>,
	James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: copy offload support in Linux - new system call needed?
Date: Thu, 15 Dec 2011 10:52:13 -0500	[thread overview]
Message-ID: <20111215155213.GF18252@shiny> (raw)
In-Reply-To: <1323961140.14317.2.camel@lade.trondhjem.org>

On Thu, Dec 15, 2011 at 09:59:00AM -0500, Trond Myklebust wrote:
> On Wed, 2011-12-14 at 17:27 -0500, J. Bruce Fields wrote: 
> > On Wed, Dec 14, 2011 at 02:42:38PM -0500, Ric Wheeler wrote:
> > > On 12/14/2011 02:27 PM, Al Viro wrote:
> > > >On Wed, Dec 14, 2011 at 02:22:07PM -0500, Ric Wheeler wrote:
> > > >
> > > >>We had an active thread a couple of years back that came out of the
> > > >>reflink work and, at the time, there seemed to be moderately
> > > >>positive support for adding a new system call that would fit this
> > > >>use case (Joel Becker's copyfile()).
> > > >>
> > > >>Can we resurrect this effort? Is copyfile() still a good way to go,
> > > >>or should we look at other hooks?
> > > >copyfile(2) is probably a good way to go, provided that we do _not_
> > > >go baroque as it had happened the last time syscall had been discussed.
> > > >
> > > >IOW, to hell with progress reports, etc. - just a fastpath kind of
> > > >thing, in the same kind of relationship to cp(1) as rename(2) is to mv(1).
> > > >If it works - fine, if not - caller has to be ready to deal with handling
> > > >cross-device case anyway.
> > > 
> > > I think that this approach makes a lot of sense. Most of the
> > > devices/targets that support the copy offload, will do it in very
> > > reasonable amounts of time.
> > 
> > The current NFSv4.2 draft rolls both the "fast" and "slow" cases into
> > one operation:
> > 
> > 	http://tools.ietf.org/html/draft-ietf-nfsv4-minorversion2-06#section-2
> >  
> > Perhaps we should ask for separate operations for the two cases.  (Or at
> > least a "please don't bother if this is going to take 8 hours" flag....)
> 
> How would the server know? I suggest we deal with this by adding an
> ioctl() to allow the application to poll for progress: I'm assuming now
> that we don't expect more than 1 copyfile() system call at a time per
> file descriptor...

If we're using this to copy VM image files, I could easily imagine
wanting to clone multiple copies of the VM in parallel.

-chris


  reply	other threads:[~2011-12-15 15:52 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14 19:22 copy offload support in Linux - new system call needed? Ric Wheeler
2011-12-14 19:22 ` Ric Wheeler
2011-12-14 19:27 ` Al Viro
2011-12-14 19:42   ` Ric Wheeler
2011-12-14 19:42     ` Ric Wheeler
2011-12-14 22:27     ` J. Bruce Fields
2011-12-14 22:27       ` J. Bruce Fields
2011-12-15 14:59       ` Trond Myklebust
2011-12-15 15:52         ` Chris Mason [this message]
2011-12-15 16:00           ` Trond Myklebust
2011-12-15 16:00             ` Trond Myklebust
2011-12-15 16:03           ` Jeff Layton
2011-12-15 16:03             ` Jeff Layton
2011-12-15 16:06             ` Trond Myklebust
2011-12-15 16:06               ` Trond Myklebust
2011-12-15 16:16               ` Jeff Layton
2011-12-15 16:16                 ` Jeff Layton
2011-12-15 16:38                 ` Trond Myklebust
2011-12-15 16:08         ` Loke, Chetan
2011-12-15 16:08           ` Loke, Chetan
2011-12-15 16:08           ` Loke, Chetan
2011-12-15 16:11           ` Trond Myklebust
2011-12-15 16:11             ` Trond Myklebust
2011-12-15 16:40             ` Loke, Chetan
2011-12-15 16:40               ` Loke, Chetan
2011-12-15 16:40               ` Loke, Chetan
2011-12-15 16:53               ` Trond Myklebust
2011-12-15 17:18                 ` Ric Wheeler
2011-12-15 17:18                   ` Ric Wheeler
2011-12-15 17:25                   ` Trond Myklebust
2011-12-15 17:31                   ` Loke, Chetan
2011-12-15 17:31                     ` Loke, Chetan
2011-12-15 17:31                     ` Loke, Chetan
2011-12-15 17:55                     ` Ric Wheeler
2011-12-15 17:27                 ` Loke, Chetan
2011-12-15 17:27                   ` Loke, Chetan
2011-12-15 17:27                   ` Loke, Chetan
2011-12-15 17:44         ` J. Bruce Fields
2011-12-15 17:44           ` J. Bruce Fields
2011-12-16  8:00     ` Joel Becker
2011-12-14 19:59 ` Jeremy Allison
2011-12-14 20:30   ` Ric Wheeler
2011-12-14 20:30     ` Ric Wheeler
2011-12-19 12:38     ` Hannes Reinecke
2011-12-19 12:38       ` Hannes Reinecke
2011-12-19 22:19   ` H. Peter Anvin
2011-12-19 22:19     ` H. Peter Anvin
2011-12-19 22:34     ` Jeremy Allison
2011-12-19 22:57     ` Dave Chinner
2011-12-19 23:29       ` H. Peter Anvin
2011-12-19 23:29         ` H. Peter Anvin

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=20111215155213.GF18252@shiny \
    --to=chris.mason@oracle.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=akpm@linux-foundation.org \
    --cc=bfields@fieldses.org \
    --cc=hare@suse.de \
    --cc=jlbec@evilplan.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=ricwheeler@gmail.com \
    --cc=viro@ZenIV.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.