From owner-freebsd-stable@FreeBSD.ORG Wed Nov 24 21:43:40 2010 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 791B910657C4 for ; Wed, 24 Nov 2010 21:43:40 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.freebsd.org (Postfix) with ESMTP id 2FEC08FC1B for ; Wed, 24 Nov 2010 21:43:39 +0000 (UTC) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id oAOLfpqm009543; Wed, 24 Nov 2010 13:43:39 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 24 Nov 2010 13:42:53 -0800 Message-ID: In-Reply-To: <20101124171510.GA27702@icarus.home.lan> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: upd: 7.2->8.1 & many networks trouble & flowtable Thread-Index: AcuL+9YgeDobanOsSh24UxfH1dxK9QAIs2Tg References: <201010230159.o9N1xGGF098363@lava.sentex.ca> <201010230821.o9N8LVuR001382@lava.sentex.ca> <20101023091555.W66242@maildrop.int.zabbadoz.net> <20101123175100.V24596@maildrop.int.zabbadoz.net> <4CECDC89.7070706@yartv.ru> <4CECFF49.2010204@yartv.ru> <20101124171510.GA27702@icarus.home.lan> From: "Li, Qing" To: "Jeremy Chadwick" Cc: Andrey Groshev , "Li, Qing" , freebsd-stable@freebsd.org Subject: RE: upd: 7.2->8.1 & many networks trouble & flowtable 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: Wed, 24 Nov 2010 21:43:40 -0000 >=20 > Here's an example of where disabling the flowtable solved a user's > problem in October 2010: >=20 > http://forums.freebsd.org/showthread.php?t=3D18301 >=20 > > Additionally I remember 2 or 3 posts to mailing lists here discussing > how bgpd was taking up 100% CPU (or specifically an entire CPU core). > I'm not sure what people did to solve that problem, but one has to > wonder if flowtable was the cause and they simply didn't realise it. > The context of the discussion was Andrey's original email, in which he reported multiple issues that include the em driver, routing daemons, flow-table garbage collector taking 100% CPU etc. The last issue obviously relates to the flow-table code, and I was not disputing about that. I simply asked for a clarification, which I did not receive a clear answer, on whether there are routing issues when flow-table is disabled. The reason why I asked, is because L2/L3 separation work (poorly named, of course) is more about the routing infrastructure changes in the FBSD 8.0 kernel, whereas the flow-table enhancements deal more with the connections (as detailed in my last email), and it builds on top of the L2/L3 work. >=20 > I can't speak for the OP or his situation -- flowtable appears to "work > fine for me", but then again none of our RELENG_8 systems do routing nor > handle large numbers of routes (very simple single-IP or multi-IP > systems on two networks). >=20 See above paragraph ... I am going to change the flow-table default setting to "disabled" for the=20 upcoming 8.2 release while these issues are being resolved, and the=20 documentation is being put in place.=20 =20 Sounds reasonable. -- Qing