All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever III <chuck.lever@oracle.com>
To: Bruce Fields <bfields@fieldses.org>
Cc: Steve Dickson <steved@redhat.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/1] Enable inter server to server copies on a export
Date: Mon, 1 Nov 2021 16:55:45 +0000	[thread overview]
Message-ID: <93DAB7C7-D0BB-48BA-9BFF-2821D88582EA@oracle.com> (raw)
In-Reply-To: <20211101154046.GA12965@fieldses.org>


> On Nov 1, 2021, at 11:40 AM, J. Bruce Fields <bfields@fieldses.org> wrote:
> 
> On Mon, Nov 01, 2021 at 11:30:48AM -0400, Steve Dickson wrote:
>> Hey!
>> 
>> On 10/29/21 15:14, J. Bruce Fields wrote:
>>> On Fri, Oct 29, 2021 at 01:30:36PM -0400, Steve Dickson wrote:
>>>> On 10/29/21 12:40, J. Bruce Fields wrote:
>>>>> Let's just stick with that for now, and leave it off by default until
>>>>> we're sure it's mature enough.  Let's not introduce new configuration to
>>>>> work around problems that we haven't really analyzed yet.
>>>> How is this going to find problems? At least with the export option
>>>> it is documented
>>> 
>>> That sounds fixable.  We need documentation of module parameters anyway.
>> Yeah I just took I don't see any documentation of module
>> parameters anywhere for any of the modules. But by documentation
>> I meant having the feature in the exports(5) manpage.
> 
> I think I'd probably create a new page for sysctls (this isn't the only
> one needing documentation), and make sure it's listed in the "SEE ALSO"
> section of the other man pages.

Aren't sysctls documented under Documentation/ ?


>>>> and it more if a stick you toe in the pool verses
>>>> jumping in...
>>> 
>>> If we want more fine-grained control, I'm not yet seeing the argument
>>> that an export option on the destination server side is the way to do
>>> it.
>>> 
>>> Let's document the module parameter and go with that for now.
>> Now that cp will use copy_file_range() when available,
>> what are the steps needed to enable these fast copies?
> 
> 1) Make sure client and both servers support NFSv4.2 and
> server-to-server copy.
> 
> 2) Make sure destination server can access (at least for read) any
> exports on the source that you want to be able to copy from.
> 
> 3) echo 1 >/sys/module/nfsd/parameters/inter_copy_offload_enable on the
> destination server.
> 
> --b.

--
Chuck Lever




  reply	other threads:[~2021-11-01 16:56 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-28 14:48 [PATCH 0/1] Enable inter server to server copies on a export Steve Dickson
2021-10-28 14:48 ` [PATCH 1/1] nfsd4_copy: Adds the ability to do inter server to server on an export Steve Dickson
2021-10-29 13:45 ` [PATCH 0/1] Enable inter server to server copies on a export J. Bruce Fields
2021-10-29 14:26   ` J. Bruce Fields
2021-10-29 15:24     ` Steve Dickson
2021-10-29 14:56   ` Steve Dickson
2021-10-29 16:40     ` J. Bruce Fields
2021-10-29 17:30       ` Steve Dickson
2021-10-29 19:14         ` J. Bruce Fields
2021-11-01 15:30           ` Steve Dickson
2021-11-01 15:40             ` J. Bruce Fields
2021-11-01 16:55               ` Chuck Lever III [this message]
2021-11-01 18:24                 ` Steve Dickson
2021-11-01 18:39                 ` Bruce Fields
2021-11-01 18:44                   ` Chuck Lever III
2021-11-01 19:10                   ` Steve Dickson
2021-11-01 19:26                     ` Bruce Fields
2021-11-01 20:28                       ` Steve Dickson
2021-11-01 19:02               ` Steve Dickson
2021-11-01 19:22                 ` dai.ngo
2021-11-01 19:25                   ` J. Bruce Fields
2021-11-01 20:25                     ` Steve Dickson
2021-10-28 14:59 Steve Dickson

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=93DAB7C7-D0BB-48BA-9BFF-2821D88582EA@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=steved@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.