linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Olga Kornievskaia <kolga@netapp.com>, linux-fsdevel@vger.kernel.org
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/1] [RFC] 64bit copy_file_range system call
Date: Wed, 14 Jun 2017 14:50:46 -0700	[thread overview]
Message-ID: <142a7dbc-0a53-0f10-b8ed-73a896a4264d@infradead.org> (raw)
In-Reply-To: <20170614185335.58193-1-kolga@netapp.com>

On 06/14/17 11:53, Olga Kornievskaia wrote:
> This is a proposal to allow 64bit count to copy and return as
> a result of a copy_file_range. No attempt was made to share code
> with the 32bit function because 32bit interface should probably
> get depreciated.

      deprecated.

> 
> Why use 64bit? Current uses of 32bit are by clone_file_range()
> which could use 64bit count and NFS copy_file_range also supports
> 64bit count value.
> 
> Also with this proposal off-the-bet allow the userland to copy

what does "off-the-bet" mean?

> between different mount points.
> 
> Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
> ---
>  arch/x86/entry/syscalls/syscall_32.tbl |   1 +
>  arch/x86/entry/syscalls/syscall_64.tbl |   1 +
>  fs/read_write.c                        | 146 +++++++++++++++++++++++++++++++--
>  include/linux/fs.h                     |   4 +
>  include/linux/syscalls.h               |   3 +
>  include/uapi/asm-generic/unistd.h      |   4 +-
>  kernel/sys_ni.c                        |   1 +
>  7 files changed, 154 insertions(+), 6 deletions(-)


-- 
~Randy

  parent reply	other threads:[~2017-06-14 21:50 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 [this message]
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
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=142a7dbc-0a53-0f10-b8ed-73a896a4264d@infradead.org \
    --to=rdunlap@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).