-
Notifications
You must be signed in to change notification settings - Fork 16
support ssl? #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
We have no plans for SSL yet. Question 2 is a huge topic. I'll try to make it short. The key difference of Libtpa and F-Stack (and all other open source userspace TCP stacks I'm aware of) is that Libtpa can coexist with the Linux kernel networking stack. More info can be found here. Besides that, F-Stack is built on top of FreeBSD, therefore, it has a mature TCP implementation. It's one of the very few TCP stacks that do not support multiple thread mode. It does support multiple process mode though. Libtpa is built from scratch, therefore, it's lightweight and high performance: Libtpa has native zero copy read and write support since the beginning. It's designed mainly for data center usage; it doesn't even support IP fragments, therefore, it might not be a good option for public internet. |
thanks, 多谢老铁! |
Unfortunately, Libtpa should not work on ec2 as it relies on a NIC feature. Libtpa currently works with Mellanox and Intel E810 NIC only. |
好,多谢老铁热忱回答; |
The text was updated successfully, but these errors were encountered: