From: Steve Dickson <SteveD@RedHat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/7 V4] The NFSv4 only mounting daemon.
Date: Thu, 4 Mar 2021 11:31:53 -0500 [thread overview]
Message-ID: <4204cd8e-f8c4-103e-bb69-a6bf720e65e9@RedHat.com> (raw)
In-Reply-To: <20210304140617.GB17512@fieldses.org>
On 3/4/21 9:06 AM, J. Bruce Fields wrote:
> On Thu, Mar 04, 2021 at 08:57:28AM -0500, Steve Dickson wrote:
>> Personally I see this is the first step away from V3...
>>
>> So what we don't need is all that RPC code, all the different mounting
>> versions... no RPC code at all, which also means no need for libtirpc...
>> That is a lot of code that goes away, which I think is a good thing.
>
> libtirpc is a shared library, it'll still be loaded as long as anyone
> needs it, and I'm not convinced we'll be able to get rid of all users.
>
>> I never thought it was a good idea to have mountd process
>> the v4 upcalls... I always thought it should be a different
>> deamon... and now we have one.
>>
>> A simple daemon that only processes v4 upcalls.
>
> I really do get the appeal, I've always liked the idea too.
>
> I'm not sure it's bringing us a real practical advantage at this point,
> compared to rpc.mountd, which can act either as a daemon that only
> processes v4 upcalls or can do both, depending on how you start it.
Right with some configuration changes... But I do think there is
value with have a package that will work right out of the box!
Boom! Install the package and you have a working v4 server
with no configure changes... I do think there is value there.
steved.
next prev parent reply other threads:[~2021-03-04 16:32 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 20:08 [PATCH 0/7 V4] The NFSv4 only mounting daemon Steve Dickson
2021-02-19 20:08 ` [PATCH 1/7] exportd: the initial shell of the v4 export support Steve Dickson
2021-02-19 20:08 ` [PATCH 2/7] exportd: Moved cache upcalls routines into libexport.a Steve Dickson
2021-02-23 16:13 ` [PATCH] exportd: server-side gid management Daniel Kobras
2021-03-04 21:28 ` Steve Dickson
2021-02-19 20:08 ` [PATCH 3/7] exportd: multiple threads Steve Dickson
2021-02-19 20:08 ` [PATCH 4/7] exportd/exportfs: Add the state-directory-path option Steve Dickson
2021-02-19 20:08 ` [PATCH 5/7] exportd: Enabled junction support Steve Dickson
2021-02-19 20:08 ` [PATCH 6/7] exportd: systemd unit files Steve Dickson
2021-02-19 20:08 ` [PATCH 7/7] exportd: Added config variable to compile in the NFSv4 only server Steve Dickson
2021-02-20 16:33 ` [PATCH 0/7 V4] The NFSv4 only mounting daemon Steve Dickson
2021-02-24 20:30 ` J. Bruce Fields
2021-03-02 22:33 ` Steve Dickson
2021-03-03 15:23 ` J. Bruce Fields
2021-03-03 21:22 ` Steve Dickson
2021-03-03 21:54 ` J. Bruce Fields
2021-03-03 22:07 ` Steve Dickson
2021-03-03 22:17 ` J. Bruce Fields
2021-03-04 13:57 ` Steve Dickson
2021-03-04 14:06 ` J. Bruce Fields
2021-03-04 16:31 ` Steve Dickson [this message]
2021-03-05 14:36 ` J. Bruce Fields
2021-03-05 15:53 ` Chuck Lever
2021-03-04 13:42 ` Steve Dickson
2021-03-04 14:01 ` J. Bruce Fields
2021-03-04 16:47 ` Steve Dickson
2021-03-04 21:31 ` Patrick Goetz
2021-03-04 13:34 ` Steve Dickson
2021-03-04 14:24 ` J. Bruce Fields
2021-03-04 16:20 ` Steve Dickson
2021-02-24 20:49 ` J. Bruce Fields
2021-03-02 22:39 ` Steve Dickson
2021-03-03 18:10 ` Chuck Lever
2021-03-03 21:24 ` 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=4204cd8e-f8c4-103e-bb69-a6bf720e65e9@RedHat.com \
--to=steved@redhat.com \
--cc=bfields@fieldses.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).