home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.nfs
- Path: sparky!uunet!spool.mu.edu!uwm.edu!ux1.cso.uiuc.edu!news.iastate.edu!john
- From: john@iastate.edu (John Hascall)
- Subject: Re: NFS packet size
- Message-ID: <C06KI1.5qJ@news.iastate.edu>
- Sender: news@news.iastate.edu (USENET News System)
- Organization: Iowa State University, Ames, IA
- References: <1992Dec31.201252.4908@prl.dec.com> <C05ICp.CF0@news.iastate.edu> <1993Jan1.115015.17311@prl.dec.com>
- Date: Fri, 1 Jan 1993 15:03:37 GMT
- Lines: 19
-
- boyd@prl.dec.com (Boyd Roberts) writes:
- }john@iastate.edu (John Hascall) writes:
-
- }> A dropped TCP fragment can result in a large amount of resending too.
-
- }True, but that all happens at the TCP/IP level which is far more
- }responsive than NFS's 1, 2, 4, 8 ... _second_ exponential backoff
- }when a datagram gets lost.
-
- Ummm, sure if you set timeo=10 (timeo is in tenths of a second)
- [admittedly, I would guess most TCP implementations are more
- responsive than .1 sec].
-
- John
- --
- John Hascall ``An ill-chosen word is the fool's messenger.''
- Systmes Software Engineer
- Project Vincent
- Iowa State University Computation Center + Ames, IA 50011 + 515/294-9551
-