Date: Fri, 8 Mar 1996 13:22:48 -0800 From: Matthew Dillon <dillon@backplane.com> To: "Garrett A. Wollman" <wollman@lcs.mit.edu> Cc: bugs@freebsd.org Subject: Re: bug in netinet/tcp_input.c Message-ID: <199603082122.NAA02648@apollo.backplane.com>
next in thread | raw e-mail | index | archive | help
:<<On Fri, 8 Mar 1996 12:36:15 -0800, Matthew Dillon <dillon@backplane.com> said:
:
:> Hmmm. Then what is the use of -recvpipe and -sendpipe ?
:
:As I said before, they are to set the default buffer size. Anything
:more complicated than that voids your warranty...
:
:-GAWollman
:
:--
:Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ...
:wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance.
:Opinions not those of| It is a bond more powerful than absence. We like people
:MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant
Is this supposed to be funny?
Look, you guys are already using locked route table fields for minimum
and maximum limits, it can't hurt to use the same mechanism for the mtu
field as well, as a 'maximum'.
Regarding -recvpipe and -sendpipe... sure, if you want to leave those
route table fields braindamaged, I suppose you can just be cute and
forget about it. Personally, it doesn't increase my respect for the
FreeBSD core team when the best answer they can give is a wise crack.
I would rather see these fields be put to good rather then made useless.
--
Also, tp->t_srtt is not being calculated correctly... I just ran some
tcp echo tests and it's nearly four times what it's supposed to be.
It gets it right sometimes, but a single lost packet out of 30 destroys
the smoothing function for some reason. I haven't traced it down yet.
-Matt
Matthew Dillon Engineering, BEST Internet Communications, Inc.
<dillon@apollo.backplane.com>
[always include a portion of the original email in any response!]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603082122.NAA02648>