diff options
| author | Chuck Lever <[email protected]> | 2017-12-04 14:13:38 -0500 |
|---|---|---|
| committer | Trond Myklebust <[email protected]> | 2018-01-14 23:06:30 -0500 |
| commit | 530ea4219231e62341f79a5517d7b4f12ec3b74f (patch) | |
| tree | e0998b983e33b87a37627a9b2d42ff45facee9ea /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | fb455baad6fc4de77d762e89dae75c2e2aa98559 (diff) | |
nfs: Referrals should use the same proto setting as their parent
Helen Chao <[email protected]> noticed that when a user
traverses a referral on an NFS/RDMA mount, the resulting submount
always uses TCP.
This behavior does not match the vers= setting when traversing
a referral (vers=4.1 is preserved). It also does not match the
behavior of crossing from the pseudofs into a real filesystem
(proto=rdma is preserved in that case).
The Linux NFS client does not currently support the
fs_locations_info attribute. The situation is similar for all
NFSv4 servers I know of. Therefore until the community has broad
support for fs_locations_info, when following a referral:
- First try to connect with RPC-over-RDMA. This will fail quickly
if the client has no RDMA-capable interfaces.
- If connecting with RPC-over-RDMA fails, or the RPC-over-RDMA
transport is not available, use TCP.
Reported-by: Helen Chao <[email protected]>
Signed-off-by: Chuck Lever <[email protected]>
Signed-off-by: Trond Myklebust <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions