Page MenuHomeFreeBSD

Add support to the NFSv4.1 client for use of a single OpenOwner for all Opens
ClosedPublic

Authored by rmacklem on Dec 29 2016, 9:54 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Apr 19, 5:40 AM
Unknown Object (File)
Fri, Apr 12, 6:47 PM
Unknown Object (File)
Fri, Apr 12, 5:48 PM
Unknown Object (File)
Fri, Apr 12, 12:48 PM
Unknown Object (File)
Mar 14 2024, 11:15 AM
Unknown Object (File)
Mar 14 2024, 11:14 AM
Unknown Object (File)
Mar 14 2024, 11:14 AM
Unknown Object (File)
Mar 14 2024, 11:14 AM
Subscribers
None

Details

Summary

Some NFSV4.1 servers, such as AmazonEFS, have very low limits for the number of
OpenOwners. As such, the default of an OpenOwner/process can easily exceed this
limit. Since NFSv4.1 allows multiple concurrent Opens on an OpenOwner, using a
single OpenOwner for all Opens is practical.

This patch (still experimental) does this via a new NFS mount option called "oneopenown"
which can only be applied to NFSv4.1 mounts.

Test Plan

I have done minimal testing and cperciva@ is testing against an AmazonEFS service.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

rmacklem retitled this revision from to Add support to the NFSv4.1 client for use of a single OpenOwner for all Opens.
rmacklem updated this object.
rmacklem edited the test plan for this revision. (Show Details)
rmacklem added a reviewer: cperciva.

I have added cperciva@ as a reviewer, since he is doing the testing.
He may not actually be willing to review the code.
Anyone else wishing to review this is welcome to do so.

The question is more whether I'm *able* to usefully review rather than whether I'm *willing*. :-)

Two parts of the patch have been removed, since they are already committed to head/current.
They were fixes not specific to using a single open_owner in an NFSv4.1 mount.

This revision was automatically updated to reflect the committed changes.