From owner-freebsd-net@FreeBSD.ORG Tue Jan 6 15:12:17 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C3A31065678; Tue, 6 Jan 2009 15:12:17 +0000 (UTC) (envelope-from ericlin@tamama.org) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by mx1.freebsd.org (Postfix) with ESMTP id 3AA888FC1A; Tue, 6 Jan 2009 15:12:17 +0000 (UTC) (envelope-from ericlin@tamama.org) Received: by yx-out-2324.google.com with SMTP id 8so3400179yxb.13 for ; Tue, 06 Jan 2009 07:12:16 -0800 (PST) Received: by 10.151.111.1 with SMTP id o1mr970543ybm.88.1231254736021; Tue, 06 Jan 2009 07:12:16 -0800 (PST) Received: by 10.151.68.13 with HTTP; Tue, 6 Jan 2009 07:12:15 -0800 (PST) Message-ID: <47713ee10901060712g7b4a204fq73cabb99c7070929@mail.gmail.com> Date: Tue, 6 Jan 2009 23:12:15 +0800 From: "Lin Jui-Nan Eric" To: "Robert Watson" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47713ee10812301206j12b35264o715976c154080a1b@mail.gmail.com> <47713ee10901012147k1f25c31bn512dd29b2b294ad5@mail.gmail.com> <47713ee10901012249w65c659bbp3366e4d8ef25c59d@mail.gmail.com> <47713ee10901052025y26d342f6me0aea946a49b6f0a@mail.gmail.com> Cc: freebsd-net@freebsd.org, stable@freebsd.org Subject: Re: TCP packet out-of-order problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jan 2009 15:12:18 -0000 Oops, we surely have kern.ipc.nmbclusters="0" in loader.conf, but I think that should not modify net.inet.tcp.reass.maxsegments to "0" since we wish unlimited nmbclusters but not zero TCP reassembly segments. On Tue, Jan 6, 2009 at 4:16 PM, Robert Watson wrote: > > On Tue, 6 Jan 2009, Lin Jui-Nan Eric wrote: > >> I thought that the system auto-tune improperly in this case. > > Hmm. Do you have a custom setting for kern.ipc.nmbclusters in loader.conf > or sysctl.conf? What does kern.ipc.nmbclusters configure itself to on your > system? Also, could you send me the output of uname -a on the system? > > Thanks, > > Robert N M Watson > Computer Laboratory > University of Cambridge > >> On Mon, Jan 5, 2009 at 9:13 PM, Robert Watson wrote: >>> >>> On Fri, 2 Jan 2009, Lin Jui-Nan Eric wrote: >>> >>>> After running "netstat -s -p tcp", we found that lots of packets are >>>> discarded due to memory problems. We googled for it, and found that >>>> sysctl >>>> oid "net.inet.tcp.reass.maxsegments" became 0, therefore packets never >>>> reassembled. >>>> >>>> Then we checked our /boot/loader.conf and /etc/sysctl.conf, and found >>>> that >>>> setting kern.ipc.nmbclusters="0" makes net.inet.tcp.reass.maxsegments=0. >>>> After setting net.inet.tcp.reass.maxsegments="1600" in >>>> /boot/loader.conf, >>>> the network works perfectly now. >>> >>> Was it set to 0 through a configuration error, or did the system >>> auto-tune >>> improperly? >>> >>> Robert N M Watson >>> Computer Laboratory >>> University of Cambridge >>> >>>> >>>> Thank you all for the help! >>>> _______________________________________________ >>>> freebsd-stable@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>>> To unsubscribe, send any mail to >>>> "freebsd-stable-unsubscribe@freebsd.org" >>>> >>> >> >