From: Zach Brown <zab@redhat.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-btrfs@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: [PATCH RFC 0/3] simple copy offloading system call
Date: Fri, 10 Apr 2015 15:00:33 -0700 [thread overview]
Message-ID: <1428703236-24735-1-git-send-email-zab@redhat.com> (raw)
Hello everyone!
Here's my current attempt at the most basic system call interface for
offloading copying between files. The system call and vfs function
are relatively light wrappers around the file_operation method that
does the heavy lifting.
There was interest at LSF in getting the basic infrastructure merged
before worrying about adding behavioural flags and more complicated
implementations. This series only offers a refactoring of the btrfs
clone ioctl as an example of an implementation of the file
copy_file_range method.
I've added support for copy_file_range() to xfs_io in xfsprogs and
have the start of an xfstest that tests the system call. I'll send
those to fstests@.
So how does this look?
Do we want to merge this and let the NFS and block XCOPY patches add
their changes when they're ready?
- z
next reply other threads:[~2015-04-10 22:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 22:00 Zach Brown [this message]
2015-04-10 22:00 ` [PATCH RFC 1/3] vfs: add copy_file_range syscall and vfs helper Zach Brown
[not found] ` <1428703236-24735-2-git-send-email-zab-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-04-10 22:36 ` Trond Myklebust
2015-04-11 0:02 ` Zach Brown
2015-04-11 0:24 ` Trond Myklebust
2015-04-11 13:04 ` Jeff Layton
2015-04-13 16:32 ` Zach Brown
2015-04-14 16:53 ` Christoph Hellwig
2015-04-14 16:58 ` Christoph Hellwig
[not found] ` <20150414165344.GA21421-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-04-14 17:16 ` Anna Schumaker
[not found] ` <552D4B5D.3090904-ZwjVKphTwtPQT0dZR+AlfA@public.gmane.org>
2015-04-14 18:19 ` J. Bruce Fields
[not found] ` <20150414181911.GA2080-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2015-04-14 18:22 ` Zach Brown
[not found] ` <20150414182241.GB23129-fypN+1c5dIyjpB87vu3CluTW4wlIGRCZ@public.gmane.org>
2015-04-14 18:29 ` J. Bruce Fields
[not found] ` <20150414182906.GB2080-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2015-04-14 18:54 ` Zach Brown
[not found] ` <20150414185408.GC23129-fypN+1c5dIyjpB87vu3CluTW4wlIGRCZ@public.gmane.org>
2015-04-14 19:23 ` Christoph Hellwig
[not found] ` <20150414192325.GB20599-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-04-14 20:04 ` Zach Brown
2015-04-10 23:01 ` Andreas Dilger
2015-04-10 22:00 ` [PATCH RFC 2/3] x86: add sys_copy_file_range to syscall tables Zach Brown
2015-04-10 22:00 ` [PATCH RFC 3/3] btrfs: add .copy_file_range file operation Zach Brown
2015-04-14 17:08 ` Chris Mason
[not found] ` <1428703236-24735-1-git-send-email-zab-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-06 6:15 ` [PATCH RFC 0/3] simple copy offloading system call Michael Kerrisk
2015-05-07 2:52 ` Andy Lutomirski
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=1428703236-24735-1-git-send-email-zab@redhat.com \
--to=zab@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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).