10Gbit/s full TX wirespeed smallest packet size on a single CPU core
netoptimizer.blogspot.com
netoptimizer.blogspot.com
[1] http://www.xilinx.com/products/silicon-devices/fpga/virtex-u...
If you're using more realist payload (eg. larger packets) you should be able to scale it further. eg 40Gbit
Bottleneck in this ongoing story has been CPU... that's because of how the software was written. So the issues have been package scheduling, synchronization (locking overhead), high level software (TCP layer, and packet filtering).
Here are more details about the original problem and the test case: https://lwn.net/Articles/629155
Some tl;dr highlights:
* the 84B packets are designed to simulate the latency characteristics of 100Gbit/s ethernet on 10Gbit/s hardware
* 2 cache misses are enough to blow the time budget for processing a packet
* The overhead of 1 syscall on SElinux is itself enough to blow the time budget
* Big picture strategy: batch packets, allocs, etc
How is CPU the bottleneck if what can be achieved with 11 CPUs can also be achieved with 1 CPU just by changing the software? If what you say is accurate, then kernel/userspace software is the bottleneck.
It's impressive, but I can't see its application. Does that mean that it will scale well to many different types of traffic? Are there extremely low-latency applications that need these tiny frames and yet want to use 10GbE?
> If you're using more realist payload (eg. larger packets) you should be able to scale it further. eg 40Gbit
Yes, I would think so. I was able to saturate four 10GbE links simultaneously (using 9000 byte frames, among four separate CPU cores spanning two memory nodes). This was using ~2010 hardware using linux 2.6.27.
DDoS.
Packets Per Second attacks which you cannot filter on the edge in hardware (e.g. routers) can be quite difficult to handle in some exceptional cases. Being able to process line-rate pps is a pretty nice thing to have.
Thankfully you can usually filter these out upstream, but it's nice to have the spare capacity to absorb traffic while you figure out exactly what you need to filter. Plus you (generally) will never be able to get a filter 100% accurate, and will usually be letting some percentage of an attack through to hit your webservers. For some sites, these attacks can be in the hundreds of gigabits per second range - even 10% of that getting through can be significant.
I'm also curious, how you guys did the test, that you've actually achieved line speed? In my book, line speed means that you don't have millisecond-level gaps between packets from time to time, and it is fairly difficult both to test and to achieve on a stock kernel.
honest question: why not use dpdk / netmap for this ?
Thats pretty sexy.