public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: Steve Dickson <steved@redhat.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/1] Enable inter server to server copies on a export
Date: Fri, 29 Oct 2021 09:45:34 -0400	[thread overview]
Message-ID: <20211029134534.GA19967@fieldses.org> (raw)
In-Reply-To: <20211028144851.644018-1-steved@redhat.com>

On Thu, Oct 28, 2021 at 10:48:50AM -0400, Steve Dickson wrote:
> This kernel patch and an upcoming nfs-utils patch
> adds a new export option 's2sc' which will allow
> inter server to server copies.

They're already allowed by a module option.  Why is an export option
better?  And why should it be set on the destination server and not the
source server?

Really, first I think we should try to identify what the problem is that
we're trying to solve.

--b.

> 
> The option needs to be set on the destination server.
> 
> The idea behind the option is to allow admins the 
> ability to control which export can do these 
> types of copies.
> 
> Steve Dickson (1):
>   nfsd4_copy: Adds the ability to do inter server to server on an export
> 
>  fs/nfsd/nfs4proc.c               | 3 ++-
>  include/uapi/linux/nfsd/export.h | 1 +
>  2 files changed, 3 insertions(+), 1 deletion(-)
> 
> -- 
> 2.31.1

  parent reply	other threads:[~2021-10-29 13:45 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 ` J. Bruce Fields [this message]
2021-10-29 14:26   ` [PATCH 0/1] Enable inter server to server copies on a export 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
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
  -- strict thread matches above, loose matches on Subject: below --
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=20211029134534.GA19967@fieldses.org \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox