Linux NFS development
 help / color / mirror / Atom feed
From: "Pádraig Brady" <P@draigBrady.com>
To: Anna Schumaker <Anna.Schumaker@netapp.com>,
	linux-nfs@vger.kernel.org, linux-btrfs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
	zab@zabbo.net, viro@zeniv.linux.org.uk, clm@fb.com,
	darrick.wong@oracle.com, mtk.manpages@gmail.com,
	andros@netapp.com, hch@infradead.org
Subject: Re: [PATCH v6 5/4] copy_file_range.2: New page documenting copy_file_range()
Date: Fri, 16 Oct 2015 22:42:40 +0100	[thread overview]
Message-ID: <56216F50.7030705@draigBrady.com> (raw)
In-Reply-To: <1445029707-31549-6-git-send-email-Anna.Schumaker@Netapp.com>

It's probably worth mentioning the sparse expansion caveat
in the docs, as it's important and not obvious.

I.E. copy_file_range() could be called from, but would
still benefit from a user space app using a SEEK_{HOLE,DATA} loop.

thanks,
Pádraig.

  parent reply	other threads:[~2015-10-16 21:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 21:08 [PATCH v6 0/4] VFS: In-kernel copy system call Anna Schumaker
2015-10-16 21:08 ` [PATCH v6 1/4] vfs: add copy_file_range syscall and vfs helper Anna Schumaker
2015-10-16 21:08 ` [PATCH v6 2/4] x86: add sys_copy_file_range to syscall tables Anna Schumaker
2015-10-16 21:08 ` [PATCH v6 3/4] btrfs: add .copy_file_range file operation Anna Schumaker
2015-10-16 21:08 ` [PATCH v6 4/4] vfs: Add vfs_copy_file_range() support for pagecache copies Anna Schumaker
2015-10-16 21:08 ` [PATCH v6 5/4] copy_file_range.2: New page documenting copy_file_range() Anna Schumaker
2015-10-16 21:21   ` Andreas Dilger
2015-10-16 21:42   ` Pádraig Brady [this message]
2015-10-18 18:30   ` Christoph Hellwig
2015-10-19 20:45     ` J. Bruce Fields
2015-10-19 21:03       ` Christoph Hellwig
2015-10-20  9:41 ` [PATCH v6 0/4] VFS: In-kernel copy system call Zhao Lei

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=56216F50.7030705@draigBrady.com \
    --to=p@draigbrady.com \
    --cc=Anna.Schumaker@netapp.com \
    --cc=andros@netapp.com \
    --cc=clm@fb.com \
    --cc=darrick.wong@oracle.com \
    --cc=hch@infradead.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=zab@zabbo.net \
    /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