On Oct 17, 2015, at 12:12 PM, Jean-Baptiste COUPIAC <jeanbapti...@nfrance.com> 
wrote:

>>> ​Then I hope you are aware of the netmap-fwd (forwarding) module  that will 
>>> be published very soon ;-)
> 
> And yes, we are wainting netmap-fwd:)

I was just working with it last night. 

http://imgur.com/s75t3kM

That's two 4-core @2.4GHz RCC-DFF w/ 4GB ram (source & sink 
(!!non-production!!)) and an 8860 (8 core @ 2.4 GHz) w/ 8 GB ram and 240GB 
m-SATA (DUT).  

pkt-gen is used for load-generation. 

Of course, this is only 1Gb Ethernet, so 1.488 million 64-byte packets per 
second is easily achieved, and the system doesn't break a sweat. Only a single 
core is in use on all three boxes. CPU load (single core!) on the DUT is about 
10-13%. 

IIRC, kernel forwarding using the same  setup is ~250Kpps and the system is DUT 
is quite sluggish. 

There are several improvements planned:
First is fragmentation support and IPv6, then figuring out how to leverage > 1 
core, followed by integration with a routing daemon (quagga / bird) and adding 
support for ACLs. Maybe IPSec (in the fast path) after that. 

We'll also need to add support for NAT in the  fast path at some point, (people 
need it, but I loathe NAT.)

The goal is > 10Mpps on commodity hardware running FreeBSD with full IPv4/IPv6 
routing and ACL. This will also run on Linux and even Windows with some effort. 

The cool thing about netmap/netmap-fwd is that the host stack is still active, 
so you still have the full FreeBSD stack running on the same interfaces, and 
the interfaces configure just like stock FreeBSD. 

-- Jim 


------------------------------------------------------------------------------
_______________________________________________
Bsdrp-users mailing list
Bsdrp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bsdrp-users

Reply via email to