3 ms·
> It's basically the difference between a green field design and tacking all those innovations onto the glueball that is linux. The latter may be ugly and compl
by loeg 8y ago
> It's basically the difference between a green field design and tacking all those innovations onto the glueball that is linux. The latter may be ugly and complex, but it has the advantage of being backwards-compatible.
I'm definitely not trying to argue in favor of the paper's opinion. :-)
I just believe the author of the article would disagree that the glueball your earlier remarks describe addresses the author's concerns. They specifically say that Linux cannot be fixed to their satisfaction, or at least argue that idea.
Look for the section on page 5 headed, "Why not use kernel-bypass techniques on Linux?"
- the8472 8y agoWell, and all I am saying is that the paper, including the section you mention, don't take these latest developments into account. They're not kernel bypasses. They're driver level optimizations and traditional APIs operating on file descriptors and virtual memory aiming to solve similar problems. This stuff is very new of course, so we have to wait for something to actually integrate all those pieces and then for benchmarks.