We tsk-tsked at Windows for putting font parsing in ring 0, but Linux is determined to try and catch up.https://twitter.com/tgraf__/status/904475786622640128 …
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Is there a fundamental reason that TLS in the kernel should be faster? Bad user-space libs? Torvalds getting soft in his old age?
AFAIK, Linus hasn't ever cared much about what gets done in optional kernel modules like this. It's core kernel code that he cares about.
It's 953 lines of code behind the CONFIG_TLS option. It sounded complex but barely registers as part of the complexity of the net subsystem.
https://github.com/torvalds/linux/commit/108ea51412a7fddcd0a39efe564dffd47a033e6c?diff=unified … is the whole thing. If you're not using it, net/tls code isn't added complexity since it's a self-contained module.
The changes to the core network code are very minimal. It's just hooked up to sendpages as an uninvasive data transformation plugin system.
Understood. I think I just fondly remember the old days when the kernel was small and easy to reason about.
AFAICT, Linux has never been about minimalism. Illusions of minimalism in the past were probably actually just due to lack of resources.
However, there is a possibility that userspace networking could beat this perfect-wise, though that may require userspace fs to do so.
It's yet another optional kernel module. Not really a big deal because it's not like the userspace TLS implementations are going to go away.
Complexity in core kernel code (RCU, namespaces) impacts everyone. This is only a self-contained option. More comparable to adding drivers.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.