From owner-freebsd-stable@FreeBSD.ORG Tue Feb 28 00:17:20 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6ADAD16A420 for ; Tue, 28 Feb 2006 00:17:20 +0000 (GMT) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1AFC43D46 for ; Tue, 28 Feb 2006 00:17:19 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id k1S0HIfs074151; Mon, 27 Feb 2006 19:17:18 -0500 (EST) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3/8.13.3) with ESMTP id k1S0HHNh096280 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Feb 2006 19:17:17 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20060227191431.08594e28@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Mon, 27 Feb 2006 19:16:28 -0500 To: shih@math.jussieu.fr From: Mike Tancsa In-Reply-To: <20060227235631.GC2964@math.jussieu.fr> References: <4402F009.1000407@g-mapps.com> <6.2.3.4.0.20060227093542.086c56c0@64.7.153.2> <44031194.8000300@g-mapps.com> <6.2.3.4.0.20060227095704.085300c8@64.7.153.2> <20060227235631.GC2964@math.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: freebsd-stable@freebsd.org Subject: Re: nfs woes in FreeBSD 6.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2006 00:17:20 -0000 At 06:56 PM 27/02/2006, Albert Shih wrote: >Is there any documentation to explain a newbie like me all (I mean really >all of them) sysctl variable ? > >For example what > > net.inet.tcp.inflight.enable=0 Some have descriptions, some are talked about in man pages. eg. % sysctl -d net.inet.tcp.inflight net.inet.tcp.inflight: TCP inflight data limiting net.inet.tcp.inflight.enable: Enable automatic TCP inflight data limiting net.inet.tcp.inflight.debug: Debug TCP inflight calculations net.inet.tcp.inflight.min: Lower-bound for TCP inflight window net.inet.tcp.inflight.max: Upper-bound for TCP inflight window net.inet.tcp.inflight.stab: Inflight Algorithm Stabilization 20 = 2 packets and man tcp inflight.enable Enable TCP bandwidth-delay product limiting. An attempt will be made to calculate the bandwidth-delay product for each individual TCP connection, and limit the amount of inflight data being transmitted, to avoid building up unnecessary packets in the network. This option is recommended if you are serving a lot of data over connections with high bandwidth-delay prod- ucts, such as modems, GigE links, and fast long-haul WANs, and/or you have configured your machine to accommodate large TCP windows. In such situations, without this option, you may experience high interac- tive latencies or packet loss due to the overloading of intermediate routers and switches. Note that band- width-delay product limiting only effects the transmit side of a TCP connection. And of course, www.google.com is an excellent start as well. ---Mike