Date: Sun, 19 May 2002 20:12:12 -0700 From: Michael Sierchio <kudzu@tenebras.com> To: "Crist J. Clark" <cjc@FreeBSD.ORG> Cc: freebsd-net@FreeBSD.ORG Subject: Re: HEADS UP: ALTQ integration developer preview Message-ID: <3CE8698C.7080500@tenebras.com> References: <3CE55A9B.73EA3DE4@mindspring.com> <Pine.LNX.4.44.0205181018300.10011-100000@scribble.fsn.hu> <3CE61675.BCE2A9E1@mindspring.com> <1021717195.1466.4.camel@gurney.reilly.home> <3CE6D592.DCF73743@mindspring.com> <20020519001249.GA24012@roughtrade.net> <3CE6F653.CDE9D2B4@mindspring.com> <20020519010703.GE24468@roughtrade.net> <3CE7508D.36568484@mindspring.com> <3CE7DFFE.2090809@tenebras.com> <20020519141455.J67779@blossom.cjclark.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Crist J. Clark wrote: > On Sun, May 19, 2002 at 10:25:18AM -0700, Michael Sierchio wrote: > [snip] > > >>Back to problem of NFS over UDP -- it's not so stateless, is it? ;-) >>Remote disk access is mostly bulk transfer operations anyway, > > > A _lot_ of remote disk access is not bulk transfers, but file status > information. Okay, you're right -- my own research indicates that 'stat' is the most common operation on a file. It accounts, in numbers, for the majority of all file operations, whether local mounts or NFS. I think I'd like to revise my point -- the implementation of a protocol which was intended to be stateless, but whereby state is introduced by attempting to implement reliable delivery over UDP (where UDP datagram size may be up to 64KB) is problematic. T/TCP is interesting, but I wouldn't use it w/o some lightweight authenticator in the message. UDP works, by and large, except when it doesn't. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3CE8698C.7080500>