From owner-freebsd-bugs Fri Mar 8 15:16:06 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA20655 for bugs-outgoing; Fri, 8 Mar 1996 15:16:06 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA20602 for ; Fri, 8 Mar 1996 15:16:00 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [204.156.134.254]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id OAA02104 for ; Fri, 8 Mar 1996 14:21:59 -0800 Received: (dillon@localhost) by apollo.backplane.com (8.6.12/8.6.5) id OAA00262; Fri, 8 Mar 1996 14:21:44 -0800 Date: Fri, 8 Mar 1996 14:21:44 -0800 From: Matthew Dillon Message-Id: <199603082221.OAA00262@apollo.backplane.com> To: "Garrett A. Wollman" Cc: bugs@FreeBSD.ORG Subject: Re: bug in netinet/tcp_input.c Sender: owner-bugs@FreeBSD.ORG X-Loop: owner-bugs@FreeBSD.ORG Precedence: bulk :< 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 I guess you people aren't aware of the tricks many people play at all levels to utilize their bandwidth better. I'll describe two of them: (1) T1 connected host - 1.5 Mbps (2) frame connected host - 128K frame (3) modem connected host - 28.8 / telecommuting and serving ftp/www In all cases, the host is often dealing with SMTP, FTP, news feeds, and so on, yet must also support one or more users.. in the case of a small frame connected ISP, perhaps a dozen or two online users. It is possible to use the route table to adjust recvpipe and sendpipe buffer sizes on a per destination basis (and mss as well if you fix your code). Why would one want to do this? Simple: In order to be able to run SMTP, FTP, newsfeeds, and other services without impacting your users. You can set up the route table to automatically use a smaller mss and smaller buffer size (reducing pipelining and thus reducing buffering problems for incoming packets). The only alternative is to hack sendmail, hack ftp, hack apache, hack news, and hack the umpteen other programs to do a socket opt to reduce the buffer size, and even that does not work with the MSS negotiation for incoming connections. What does this give you? This allows you to saturate your link without degrading interactive performance over the same link. Now, unless everyone and his mother has a personal T3, being able to adjust the mss and receive and send pipes on an individual basis is an incredibly powerful tool for reaching that state. Stop thinking small... think BIG! Turn those braindead features into something more useful. -Matt Matthew Dillon Engineering, BEST Internet Communications, Inc. [always include a portion of the original email in any response!]