From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: P??draig Brady <P@draigBrady.com>
Cc: Anna Schumaker
<Anna.Schumaker-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-btrfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
zab-ugsP4Wv/S6ZeoWH0uzbU5w@public.gmane.org,
viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org,
clm-b10kYP2dOMg@public.gmane.org,
darrick.wong-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org,
mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
andros-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org,
hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org
Subject: Re: [PATCH v7 5/4] copy_file_range.2: New page documenting copy_file_range()
Date: Sun, 25 Oct 2015 20:39:25 -0700 [thread overview]
Message-ID: <20151026033925.GA9945@infradead.org> (raw)
In-Reply-To: <562B734D.50800-V8g9lnOeT5ydJdNcDFJN0w@public.gmane.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 988 bytes --]
On Sat, Oct 24, 2015 at 01:02:21PM +0100, P??draig Brady wrote:
> I'm a bit worried about the sparse expansion and default reflinking
> which might preclude cp(1) from using this call in most cases, but I will
> test and try to use it. coreutils has heuristics for determining if files
> are remote, which we might use to restrict to that use case.
Can you explain why reflinking and hole expansion are an issue if done
locally and not if done remotely? I'd really like to make the call as
usable as possible for everyone, but we really need clear semåntics for
that.
Also note that Annas current series allows for hole filling - any decent
implementation should not do them, but that's really a quality of
implementation and not an interface issue.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-10-26 3:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 19:32 [PATCH v7 0/4] VFS: In-kernel copy system call Anna Schumaker
[not found] ` <1445628736-13058-1-git-send-email-Anna.Schumaker-ZwjVKphTwtPQT0dZR+AlfA@public.gmane.org>
2015-10-23 19:32 ` [PATCH v7 1/4] vfs: add copy_file_range syscall and vfs helper Anna Schumaker
[not found] ` <1445628736-13058-2-git-send-email-Anna.Schumaker-ZwjVKphTwtPQT0dZR+AlfA@public.gmane.org>
2015-10-27 16:03 ` Steve French
2015-10-23 19:32 ` [PATCH v7 2/4] x86: add sys_copy_file_range to syscall tables Anna Schumaker
2015-10-23 19:32 ` [PATCH v7 5/4] copy_file_range.2: New page documenting copy_file_range() Anna Schumaker
2015-10-24 12:02 ` Pádraig Brady
[not found] ` <562B734D.50800-V8g9lnOeT5ydJdNcDFJN0w@public.gmane.org>
2015-10-26 3:39 ` Christoph Hellwig [this message]
[not found] ` <20151026033925.GA9945-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-10-26 12:19 ` Pádraig Brady
2015-10-26 21:41 ` J. Bruce Fields
[not found] ` <20151026214110.GA9232-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2015-10-27 11:34 ` Austin S Hemmelgarn
2015-10-23 19:32 ` [PATCH v7 3/4] btrfs: add .copy_file_range file operation Anna Schumaker
2015-10-23 19:32 ` [PATCH v7 4/4] vfs: Add vfs_copy_file_range() support for pagecache copies Anna Schumaker
2015-10-24 6:21 ` [PATCH v7 0/4] VFS: In-kernel copy system call Christoph Hellwig
2015-10-24 16:52 ` Eric Biggers
2015-10-25 5:23 ` Andreas Dilger
2015-10-26 3:45 ` Christoph Hellwig
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=20151026033925.GA9945@infradead.org \
--to=hch-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=Anna.Schumaker-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org \
--cc=P@draigBrady.com \
--cc=andros-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org \
--cc=clm-b10kYP2dOMg@public.gmane.org \
--cc=darrick.wong-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-btrfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org \
--cc=zab-ugsP4Wv/S6ZeoWH0uzbU5w@public.gmane.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).