Date: Sat, 20 Sep 2014 13:31:45 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Rumen Telbizov <telbizov@gmail.com> Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> Subject: Re: FreeBSD 10 network performance problems Message-ID: <CAJ-Vmo=M-Z%2Bw53jutuiA_1Fjsp3kL8=Ug3z9t-n5-6MbCRLQwQ@mail.gmail.com> In-Reply-To: <CAENR%2B_VDVvnY0zWKVXHOjz2vWw27s%2ByVrz9ZFokZ=p6P6oFNvw@mail.gmail.com> References: <CAENR%2B_VDVvnY0zWKVXHOjz2vWw27s%2ByVrz9ZFokZ=p6P6oFNvw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, The forwarding paths don't 100% use flowtable, so there's still routing table lookups. All those highly contended locks are the rtentry locking because the forwarding and fast forwarding paths don't use flowtable. This shouldn't be a difficult problem to solve; someone just has to go through those places above, figure out what code is doing the lookups and convert them to use flowtable. The one place that's currently a pain is how IPv4 redirects are handled; you can turn them off with a sysctl. -a
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=M-Z%2Bw53jutuiA_1Fjsp3kL8=Ug3z9t-n5-6MbCRLQwQ>