From owner-freebsd-stable@FreeBSD.ORG Thu Nov 24 07:29:45 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 6FDD6106564A for ; Thu, 24 Nov 2011 07:29:45 +0000 (UTC) (envelope-from kristoph.bauer@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3381F8FC08 for ; Thu, 24 Nov 2011 07:29:44 +0000 (UTC) Received: by ggnk5 with SMTP id k5so3183953ggn.13 for ; Wed, 23 Nov 2011 23:29:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=8Cw7P9yURwC3OljNAxWMDzQnR49oaN1stQW9BUjVo4c=; b=va2sohBvWeNZsRGA/3yUlXOrXM9niJPxfJrNyfcTUCcHrz73ETZDL1m/kXv07vRTxU fQn0sj185FHc+6AIldu/5m/hhC3weEndp1u4uf3zb3aHVXam2XCDa+EXGEtejFbIBPLX 8NkDuJLQTFmtX1ahD/Xeqoj9prvZlVl5d7PSI= MIME-Version: 1.0 Received: by 10.50.17.199 with SMTP id q7mr31034094igd.20.1322118145761; Wed, 23 Nov 2011 23:02:25 -0800 (PST) Received: by 10.50.34.167 with HTTP; Wed, 23 Nov 2011 23:02:25 -0800 (PST) Date: Thu, 24 Nov 2011 01:02:25 -0600 Message-ID: From: Kris Bauer To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: 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 07:29:45 -0000 Hello, I am currently experiencing an issue with FreeBSD 9.0-RC2 r227852 where the net.inet.tcp.reass.curesegments value is constantly increasing (and not descreasing when there is nominal traffic with the box). It is causing tcp slowdowns as described with kern/155407: Exhausted net.inet.tcp.reass.maxsegments block recovering tcp session (for this socket and any other socket waiting for retransmited packets). After exhausted net.inet.tcp.reass.maxsegments allocation new entry in tcp_reass failed (for this socket and any other socket waiting for retransmited packets). I have increased the reass.maxsegments value to 16384 to temporarily avoid the problem, but the cursegments number keeps rising and it seems it will occur again. Is this an issue that anyone else has seen? I can provide more information if need be. Thanks, Kris