News for hackers. Stuff that matters.
Re:Why do we use the Linux kernel's TCP stack? by toast0 on Saturday July 02, 2016 @02:38AM (#12021635)
I've only poked at the FreeBSD TCP stack and not the Linux stack, but it seems like if the problem is locking, you should be able to get good results from working on the locking (finer grained locks / tweaking parameters) in less time than building a full tcp stack.

What kind of limitations are people seeing with the Linux kernel? If I'm interpreting Netflix's paper[1] correctly, they could push at least 20 Gbps of unencrypted content with a single socket E5-2650L (document isn't super clear though, it says they were designed for 40Gbps). My servers usually run out of application CPU before they run out of network -- but I've run some of them up to 10Gbps without a lot of tuning.

[1] https://people.freebsd.org/~rrs/asiabsd_2015_tls.pdf Context is accelerating https downloads, but some decent numbers anyway.

Re:Why do we use the Linux kernel's TCP stack? by mioelnir on Saturday July 02, 2016 @06:51AM (#12022085)
Re:Why do we use the Linux kernel's TCP stack? by yxhuvud on Saturday July 02, 2016 @09:47AM (#12022493)
Gbps is not created equal. Traffic with many small packets takes a lot more resources compared to traffic with fewer but bigger. Netflix packages would be as big as they come.
Re:Why do we use the Linux kernel's TCP stack? by bogomipz on Saturday July 02, 2016 @06:07PM (#12023946)
Yes, in fact for things like Juniper/Cisco firewalls they will always quote PPS in full MTU packets. If you want to bring that shiny new firewall to its knees try sending it traffic with the minimum MTU of 68 bytes at line rate for the NIC.
Re:Why do we use the Linux kernel's TCP stack? by toast0 on Saturday July 02, 2016 @10:18AM (#12022625)
Ah, I'm also dealing with large packets, generally.