All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: Zach Brown <zab@redhat.com>, <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: Re: [PATCH RFC 3/3] btrfs: add .copy_file_range file operation
Date: Tue, 14 Apr 2015 13:08:02 -0400	[thread overview]
Message-ID: <552D4972.9010509@fb.com> (raw)
In-Reply-To: <1428703236-24735-4-git-send-email-zab@redhat.com>

On 04/10/2015 06:00 PM, Zach Brown wrote:
> This rearranges the existing COPY_RANGE ioctl implementation so that the
> .copy_file_range file operation can call the core loop that copies file
> data extent items.
> 
> The extent copying loop is lifted up into its own function.  It retains
> the core btrfs error checks that should be shared.
> 

Thanks Zach, the btrfs bits look reasonable

Signed-off-by: Chris Mason <clm@fb.com>

-chris


WARNING: multiple messages have this Message-ID (diff)
From: Chris Mason <clm@fb.com>
To: Zach Brown <zab@redhat.com>,
	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: Re: [PATCH RFC 3/3] btrfs: add .copy_file_range file operation
Date: Tue, 14 Apr 2015 13:08:02 -0400	[thread overview]
Message-ID: <552D4972.9010509@fb.com> (raw)
In-Reply-To: <1428703236-24735-4-git-send-email-zab@redhat.com>

On 04/10/2015 06:00 PM, Zach Brown wrote:
> This rearranges the existing COPY_RANGE ioctl implementation so that the
> .copy_file_range file operation can call the core loop that copies file
> data extent items.
> 
> The extent copying loop is lifted up into its own function.  It retains
> the core btrfs error checks that should be shared.
> 

Thanks Zach, the btrfs bits look reasonable

Signed-off-by: Chris Mason <clm@fb.com>

-chris

  reply	other threads:[~2015-04-14 17:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 22:00 [PATCH RFC 0/3] simple copy offloading system call Zach Brown
2015-04-10 22:00 ` [PATCH RFC 1/3] vfs: add copy_file_range syscall and vfs helper Zach Brown
2015-04-10 22:36   ` Trond Myklebust
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
2015-04-14 17:16             ` Anna Schumaker
2015-04-14 17:16               ` Anna Schumaker
2015-04-14 17:16               ` Anna Schumaker
2015-04-14 18:19               ` J. Bruce Fields
2015-04-14 18:19                 ` J. Bruce Fields
2015-04-14 18:22                 ` Zach Brown
2015-04-14 18:22                   ` Zach Brown
2015-04-14 18:29                   ` J. Bruce Fields
2015-04-14 18:29                     ` J. Bruce Fields
2015-04-14 18:54                     ` Zach Brown
2015-04-14 18:54                       ` Zach Brown
2015-04-14 19:23                       ` Christoph Hellwig
2015-04-14 19:23                         ` Christoph Hellwig
2015-04-14 20:04                         ` Zach Brown
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 [this message]
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-06  6:15     ` 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=552D4972.9010509@fb.com \
    --to=clm@fb.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 \
    --cc=zab@redhat.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.