From: bfields@fieldses.org (J. Bruce Fields)
To: Andreas Dilger <adilger@dilger.ca>
Cc: Olga Kornievskaia <aglo@umich.edu>,
Christoph Hellwig <hch@infradead.org>,
Olga Kornievskaia <kolga@netapp.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/1] [RFC] 64bit copy_file_range system call
Date: Fri, 16 Jun 2017 13:36:30 -0400 [thread overview]
Message-ID: <20170616173630.GE12030@fieldses.org> (raw)
In-Reply-To: <D4ACE39C-B98F-4076-B9D1-9767CE76EFED@dilger.ca>
On Thu, Jun 15, 2017 at 12:35:29PM -0600, Andreas Dilger wrote:
>
> > On Jun 15, 2017, at 7:07 AM, Olga Kornievskaia <aglo@umich.edu> wrote:
> > Reason: it will not hurt any user but it will help for
> > server-to-server NFS copy because for each invocation of of
> > copy_file_range() it requires that the client sends COPY_NOTIFY, then
> > COPY and then a copy triggers a establishment of clientid/session
> > before the reading of the source file can happen. All that could be
> > saved by have a 64bit value.
>
> What is the overhead of sending a couple of RPCs vs. copying 4GB of
> data on the server?
It makes a difference in the clone case, doesn't it? (Though I'd think
best there would be a special "copy to end of file" value.)
--b.
next prev parent reply other threads:[~2017-06-16 17:36 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 17:06 [PATCH 1/1] [RFC] 64bit copy_file_range system call Olga Kornievskaia
2017-06-14 17:24 ` Anna Schumaker
2017-06-14 18:53 ` Olga Kornievskaia
2017-06-14 19:32 ` Amir Goldstein
2017-06-14 20:08 ` Olga Kornievskaia
2017-06-14 21:50 ` Randy Dunlap
2017-06-15 13:07 ` Olga Kornievskaia
2017-06-15 3:59 ` Darrick J. Wong
2017-06-15 14:39 ` Olga Kornievskaia
2017-06-15 20:53 ` Darrick J. Wong
2017-06-19 18:34 ` Olga Kornievskaia
2017-06-19 19:39 ` Christoph Hellwig
2017-06-19 19:48 ` Olga Kornievskaia
2017-06-20 12:38 ` Steve Dickson
2017-06-20 19:33 ` Chuck Lever
2017-06-20 19:37 ` Olga Kornievskaia
2017-06-24 11:29 ` Mkrtchyan, Tigran
2017-06-20 12:44 ` Steve Dickson
2017-06-15 8:15 ` Christoph Hellwig
2017-06-15 13:07 ` Olga Kornievskaia
2017-06-15 18:35 ` Andreas Dilger
2017-06-15 19:11 ` Olga Kornievskaia
2017-06-16 17:36 ` J. Bruce Fields [this message]
2017-06-17 10:03 ` Christoph Hellwig
2017-06-17 12:42 ` Olga Kornievskaia
2017-06-17 15:09 ` Christoph Hellwig
2017-06-17 18:24 ` J. Bruce Fields
2017-06-24 13:23 ` Jeff Layton
2017-06-26 13:21 ` Anna Schumaker
2017-06-26 13:46 ` Jeff Layton
2017-06-26 14:46 ` Olga Kornievskaia
2017-06-26 14:49 ` [PATCH 1/1] VFS permit cross device vfs_copy_file_range Olga Kornievskaia
2017-06-27 11:47 ` Jeff Layton
2017-06-27 16:12 ` Olga Kornievskaia
[not found] ` <5E53733A-8136-4FB5-A7E9-F4846BF98507@netapp.com>
2017-06-26 14:51 ` [PATCH 1/1] [RFC] 64bit copy_file_range system call Jeff Layton
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=20170616173630.GE12030@fieldses.org \
--to=bfields@fieldses.org \
--cc=adilger@dilger.ca \
--cc=aglo@umich.edu \
--cc=hch@infradead.org \
--cc=kolga@netapp.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@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).