Re:Why we use the Linux kernel's TCP stack
by felixgallo on Monday July 11, 2016 @11:10AM
(#12071567)
The kernel scheduler has no idea which application thread handles which socket. You can formulate an application level plan and then enforce your will with socket and cpu pinning.
[ Parent
| on HN ]
Correct, but the difficulty is if your application must share the machine with any other application - even short lived ones. That, I think, is what joosters was alluding to. If the assumption that your application is the only consumer of system resources is broken, then you may see pathological scheduling behavior.