Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 24 Nov 2010 13:42:53 -0800
From:      "Li, Qing" <qing.li@bluecoat.com>
To:        "Jeremy Chadwick" <freebsd@jdc.parodius.com>
Cc:        Andrey Groshev <greenx@yartv.ru>, "Li, Qing" <qing.li@bluecoat.com>, freebsd-stable@freebsd.org
Subject:   RE: upd: 7.2->8.1 & many networks trouble & flowtable
Message-ID:  <B583FBF374231F4A89607B4D08578A43088D51F6@bcs-mail03.internal.cacheflow.com>
In-Reply-To: <20101124171510.GA27702@icarus.home.lan>
References:  <201010230159.o9N1xGGF098363@lava.sentex.ca> <AANLkTimWTTHWC04my3CSoNGYsLarS9F10eoO=8Fz37cF@mail.gmail.com> <201010230821.o9N8LVuR001382@lava.sentex.ca> <20101023091555.W66242@maildrop.int.zabbadoz.net> <20101123175100.V24596@maildrop.int.zabbadoz.net> <AANLkTi=E89jJH68Ng1R06tKQi%2BxpaYORpktrZk5cvjVh@mail.gmail.com> <4CECDC89.7070706@yartv.ru> <A9DF1923-565F-4B43-8429-51C9D27FCC87@bluecoat.com> <4CECFF49.2010204@yartv.ru> <B583FBF374231F4A89607B4D08578A430823C9A4@bcs-mail03.internal.cacheflow.com> <20101124171510.GA27702@icarus.home.lan>

next in thread | previous in thread | raw e-mail | index | archive | help
<snip>

>=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

<snip>

>
> 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.

<snip>

>=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






Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B583FBF374231F4A89607B4D08578A43088D51F6>