diff options
| author | Chuck Lever <chuck.lever@oracle.com> | 2016-05-16 07:42:38 -0400 |
|---|---|---|
| committer | Steve Dickson <steved@redhat.com> | 2016-05-16 07:42:38 -0400 |
| commit | 959efe8fe0f5cf8882b6401efddf02cba033cb32 (patch) | |
| tree | c4c0f1490cf0800402337f01ddc3a9ba63c62d97 /utils/exportfs/exportfs.c | |
| parent | bfe62c85f3101a1840d184d82b1cf958c4fbb9c3 (diff) | |
| download | nfs-utils-959efe8fe0f5cf8882b6401efddf02cba033cb32.tar.gz nfs-utils-959efe8fe0f5cf8882b6401efddf02cba033cb32.tar.xz nfs-utils-959efe8fe0f5cf8882b6401efddf02cba033cb32.zip | |
gssd: Convert 'rdma' to 'tcp' protocol
The kernel NFS client specifies 'rdma' as the transport protocol for
NFS/RDMA mounts. This is a generic display token, probably not
something the kernel should lie about. The kernel uses it to form
NFSv4 client IDs, for example.
Until gssd can speak RPC-over-RDMA, convert 'rdma' to 'tcp' in
kernel gss upcalls.
This means that the Linux NFS client requires an NFS/TCP service on
an NFS/RDMA server when establishing a GSS context for proto=rdma
mount points. This is probably not an onerous requirement for the
time being.
Eventually user space support for RPC-over-RDMA might be introduced,
and gssd can use that for context establishment.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Steve Dickson <steved@redhat.com>
Diffstat (limited to 'utils/exportfs/exportfs.c')
0 files changed, 0 insertions, 0 deletions