Chuck Lever 6d0699a5ba NFS over TCP retransmit behavior should default to a 60 second time out, ...

mimicing the NFS reference implementation.

NFS over TCP does not need fast retransmit timeouts, since network loss
and congestion are managed by the transport (TCP), unlike with NFS over
UDP.  A long timeout prevents the unnecessary retransmission of non-
idempotent NFS requests.

Reviewed by:	mohans, silby, rees?
Sponsored by:	Network Appliance, Incorporated

2006-05-23 18:48:07 +00:00

..

bootp_subr.c

…

krpc_subr.c

…

krpc.h

…

nfs_bio.c

Changes to make the NFS client MP safe.

2006-05-19 00:04:24 +00:00

nfs_diskless.c

…

nfs_lock.c

…

nfs_lock.h

…

nfs_nfsiod.c

Changes to make the NFS client MP safe.

2006-05-19 00:04:24 +00:00

nfs_node.c

Vnode locks are recursive and the NFS client support shared vnode locks.

2006-05-23 16:07:23 +00:00

nfs_socket.c

Refactor the NFS over UDP retransmit timeout estimation logic to allow

2006-05-23 18:33:58 +00:00

nfs_subs.c

Changes to make the NFS client MP safe.

2006-05-19 00:04:24 +00:00

nfs_vfsops.c

NFS over TCP retransmit behavior should default to a 60 second time out,

2006-05-23 18:48:07 +00:00

nfs_vnops.c

Changes to make the NFS client MP safe.

2006-05-19 00:04:24 +00:00

nfs.h

NFS over TCP retransmit behavior should default to a 60 second time out,

2006-05-23 18:48:07 +00:00

nfsargs.h

…

nfsdiskless.h

…

nfsm_subs.h

…

nfsmount.h

Refactor the NFS over UDP retransmit timeout estimation logic to allow

2006-05-23 18:33:58 +00:00

nfsnode.h

Changes to make the NFS client MP safe.

2006-05-19 00:04:24 +00:00

nfsstats.h

…

nlminfo.h

…