1. Proposed title of this feature request

o NFSv4.1 Cliend ID trunking

2. Who is the customer behind the request?

Account:
TAM customer: no
CSM customer: no
Strategic: no

3. What is the nature and description of the request?

o Add additional capabilites/functionality to the shipped kernel in RHEL to allow
for NFS clients to have multiple TCP connections to the same NFS server, but for different shares,
with NFSv4.1.

4. Why does the customer need this? (List the business requirements here)

o NFSv4.1 loses the functionality present in NFSv4.0 to allow for shares to be mounted
on a per TCP basis, provided the NFS server is multi-homed. Separate TCP connections
are made for each share to prevent one NFS share from consumming all of the available
bandwidth. This is needed as there is no elevator/scheduler for RPC and there is only one RPC queue
per TCP connection. The only available means to prevent TCP multiplexing across multiple
shares is to connect to each share with a separate destination IP address.

5. How would the customer like to achieve this? (List the functional requirements here)

o Changes to the shipped kernel and userspace where appropriate.

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

o Mount a NFSv4.1 share to one IP address of a NFS server then mount a second NFSv4.1 share to the second IP address
of the NFS server. The second share should have its own TCP connection and not share the TCP connection of the
first share.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

o No.

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

o RHEL8

9. Is the sales team involved in this request and do they have any additional input?

o No

10. List any affected packages or components.

o kernel -> fs/nfs and net/sunrpc code.
o nfsutils -> adding userspace functionality if necessary.

11. Would the customer be able to assist in testing this functionality if implemented?

o Yes.