From owner-freebsd-stable@FreeBSD.ORG Thu Nov 24 20:30:47 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67AE11065686 for ; Thu, 24 Nov 2011 20:30:47 +0000 (UTC) (envelope-from kristoph.bauer@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 301BD8FC2E for ; Thu, 24 Nov 2011 20:30:46 +0000 (UTC) Received: by iakl21 with SMTP id l21so5289440iak.13 for ; Thu, 24 Nov 2011 12:30:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=aCwXMS3VuTziMvlm6w8SCGj+0FT7m9N2IjxkIrf07i0=; b=YE01wnma8mee+gfifGcaJe+ePZmc0yt06OrCfdYhRQ6vxgryK9ZyZCW/OD16TIWTgO 1hIgfEhErdU4GgA/67eTwYkwy0B6k002WM+zw3JnH9GSdHjJqjal305I8QoljQ6cwHuH K8R9bTit/o0BxEIsHCu6/1LoFVXtrfQsy8Org= MIME-Version: 1.0 Received: by 10.42.162.130 with SMTP id y2mr8432560icx.26.1322166646590; Thu, 24 Nov 2011 12:30:46 -0800 (PST) Received: by 10.50.34.167 with HTTP; Thu, 24 Nov 2011 12:30:46 -0800 (PST) In-Reply-To: <4ECE9914.6020502@turing.b2n.org> References: <4ECE9914.6020502@turing.b2n.org> Date: Thu, 24 Nov 2011 14:30:46 -0600 Message-ID: From: Kris Bauer To: Raul Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: TCP Reassembly Issues 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: Thu, 24 Nov 2011 20:30:47 -0000 On Thu, Nov 24, 2011 at 1:20 PM, Raul wrote: > El 24/11/2011 17:07, kerbzo escribi=F3: > > > I 'm experiencing a similar issue but I don't know if mine could be >> considered normal behaviour: even if net.inet.tcp.reass.curesegments >> is set to 1680 and does not icrease, the output of vmstat -z shows a >> high tcpreass fail value that I don't remember in previous (8-STABLE) >> builds: >> > > I see both, 'net.inet.tcp.reass.cursegments' reaching default > 'net.inet.tcp.reass.maxsegments' after 38 minutes of uptime, apparently f= or > never going down despite the amount of traffic and vmstat -z also show > tcpreass failures. > > I also see sudden packet 'bursts' discarded by memory problems maybe > related: > [....] > %date && netstat -s -p tcp | grep mem > jueves, 24 de noviembre de 2011, 19:39:23 CET > 5115 discarded due to memory problems > %date && netstat -s -p tcp | grep mem > jueves, 24 de noviembre de 2011, 19:39:30 CET > 5268 discarded due to memory problems > [....] > > My settings: > [....] > %cat /etc/sysctl.conf | grep -v ^\# > debug.cpufreq.lowest=3D1000 > > %cat /boot/loader.conf | grep -v ^\# > vfs.zfs.prefetch_disable=3D0 > aio_load=3D"YES" > cc_cubic_load=3D"YES" > > %sysctl net.isr > net.isr.numthreads: 1 > net.isr.maxprot: 16 > net.isr.defaultqlimit: 256 > net.isr.maxqlimit: 10240 > net.isr.bindthreads: 0 > net.isr.maxthreads: 1 > net.isr.direct: 0 > net.isr.direct_force: 0 > net.isr.dispatch: direct > [....] > > cc cubic although loaded, not used in this 'pristine' reboot. > About firewalling, pf using altq. > > Pretty recent compile: > [....] > %sysctl -a | grep RC2 > kern.osrelease: 9.0-RC2 > kern.version: FreeBSD 9.0-RC2 #0: Thu Nov 24 00:39:07 CET 2011 > [....] > > Regards, > Ra=FAl. > > _______________________________________________ > 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" > I am seeing the same sorts of things in netstat & vmstat: # netstat -s -p tcp |grep mem 742935 discarded due to memory problems # vmstat -z |grep tcpreass tcpreass: 40, 16464, 16340, 124, 131485,955443, 0 I also this filling up of reass.cursegments occur within an hour of reboot. Thanks, Kris