3 ms·
Belongs in userspace. Absolutely not the kernel. But we can't seem to move past archaic UNIX architecture.
by snvzz 1y ago
Belongs in userspace. Absolutely not the kernel.
But we can't seem to move past archaic UNIX architecture.
- mey 1y agoWhile there are issues with Window's WDM (badly writen drivers abound), it really should be looked as a model. _but_ that would require a stable ABI. Which is specifically called out as not desired here https://www.kernel.org/doc/html/next/process/stable-api-nonsense.html https://www.kernel.org/doc/html/next/process/stable-api-nons... There are valid concerns, but the analysis doesn't lay out the issues with the current design either making it a one sided review.
- JackSlateur 1y agoCould you tell more about the WDM advantages ?
- account42 1y agoMost of the graphic drivers is already in user space. What's in the kernel is there the to manage memory and handle coordinate command submission and scheduling as well as display output configuration. There is no reason why this shouldn't be in the kernel.
- cnst 1y agoBut why do we need 499MB for such simple tasks, where all the rest of the kernel combined still fits in 135MB, with all the drivers for all the other devices, including Intel graphics? I mean, it's 3.7x larger than all the rest of the kernel (135x3.7=499), how is that in any way reasonable for such a small set of functions across so few devices to take up so much space?