2 ms·
> they are sending the smallest possible ethernet ethernet frame at 84 bytes It's impressive, but I can't see its application. Does that mean that it will sc
by wyldfire 12y ago
> they are sending the smallest possible ethernet ethernet frame at 84 bytes
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.
- wtallis 12y agoMost of the processing overhead is per-packet rather than per-byte so they're testing the worst-case scenario by minimizing the size of the packets and frames, thereby maximizing the number of packets and frames. It doesn't have much direct applicability, but it does mean that the optimizations will be sufficient to achieve wire speed for any traffic pattern.
- phil21 12y ago> It's impressive, but I can't see its application. 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.