Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 07 Jul 2008 13:31:59 +0200
From:      Kris Kennaway <kris@FreeBSD.org>
To:        Andre Oppermann <andre@freebsd.org>
Cc:        FreeBSD Net <freebsd-net@freebsd.org>, Robert Watson <rwatson@FreeBSD.org>, Bart Van Kerckhove <bart@it-ss.be>, Ingo Flaschberger <if@xip.at>, Paul <paul@gtcomm.net>
Subject:   Re: Freebsd IP Forwarding performance (question, and some info) [7-stable, current, em, smp]
Message-ID:  <4871FEAF.1060501@FreeBSD.org>
In-Reply-To: <4871D81B.8070507@freebsd.org>
References:  <4867420D.7090406@gtcomm.net>	<4869B025.9080006@gtcomm.net><486A7E45.3030902@gtcomm.net>	<486A8F24.5010000@gtcomm.net><486A9A0E.6060308@elischer.org>	<486B41D5.3060609@gtcomm.net><alpine.LFD.1.10.0807021052041.557@filebunker.xip.at><486B4F11.6040906@gtcomm.net><alpine.LFD.1.10.0807021155280.557@filebunker.xip.at><486BC7F5.5070604@gtcomm.net><20080703160540.W6369@delplex.bde.org><486C7F93.7010308@gtcomm.net><20080703195521.O6973@delplex.bde.org><486D35A0.4000302@gtcomm.net><alpine.LFD.1.10.0807041106591.19613@filebunker.xip.at><486DF1A3.9000409@gtcomm.net><alpine.LFD.1.10.0807041303490.20760@filebunker.xip.at><486E65E6.3060301@gtcomm.net>	<alpine.LFD.1.10.0807052356130.2145@filebunker.xip.at>	<2d3001c8def1$f4309b90$020b000a@bartwrkstxp>	<486FFF70.3090402@gtcomm.net>	<20080706132148.E44832@fledge.watson.org> <4871D81B.8070507@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Andre Oppermann wrote:
> Robert Watson wrote:
>> Experience suggests that forwarding workloads see significant lock 
>> contention in the routing and transmit queue code.  The former needs 
>> some kernel hacking to address in order to improve parallelism for 
>> routing lookups.  The latter is harder to address given the hardware 
>> you're using: modern 10gbps cards frequently offer multiple transmit 
>> queues that can be used independently (which our cxgb driver 
>> supports), but 1gbps cards generally don't.
> 
> Actually the routing code is not contended.  The workload in router
> is mostly serialized without much opportunity for contention.  With
> many interfaces and any-to-any traffic patterns it may get some
> contention.  The locking overhead per packet is always there and has
> some impact though.
> 

Actually contention from route locking is a major bottleneck even on 
packet generation from multiple CPUs on a single host.  It is becoming 
increasingly necessary that someone look into fixing this.

Kris



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