From: Jeremy Allison <jra@samba.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jeremy Allison <jra@samba.org>,
Ric Wheeler <ricwheeler@gmail.com>,
"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: Mon, 19 Dec 2011 14:34:06 -0800 [thread overview]
Message-ID: <20111219223406.GB20631@samba2> (raw)
In-Reply-To: <4EEFB87F.9000104@zytor.com>
On Mon, Dec 19, 2011 at 02:19:43PM -0800, H. Peter Anvin wrote:
> On 12/14/2011 11:59 AM, Jeremy Allison wrote:
> >>
> >> Can we resurrect this effort? Is copyfile() still a good way to go,
> >> or should we look at other hooks?
> >
> > Windows uses a COPYCHUNK call, which specifies the
> > following parameters:
> >
> > Definition of a copy "chunk":
> >
> > hyper source_off;
> > hyper target_off;
> > uint32 length;
> >
> > and an array of these chunks which is passed
> > into their kernel.
> >
> > This is what we have to implement in Samba.
> >
>
> Could we do this by (re-)allowing sendfile() between two files?
Oooh - nice idea ! Yes, having a completely symmetric sendfile
which allows socket -> file, file -> socket, socket -> socket,
file -> file would be a great idea (IMHO).
Jeremy.
next prev parent reply other threads:[~2011-12-19 22:34 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
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 [this message]
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=20111219223406.GB20631@samba2 \
--to=jra@samba.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=hare@suse.de \
--cc=hpa@zytor.com \
--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 \
/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.