Which is why the kernel folks' insistence on keeping drivers in the kernel rather than sandboxed user processes is so backwards...https://twitter.com/CopperheadOS/status/863454511674871808 …
You don't have to accept microkernel dogma to get drivers out of kernel. Keep the whole OS model monolithic if you want. Just ban drivers!
-
-
If drivers ran in full-nobody-container with full seccomp and only got mmap (and from hardware side, iommu) access to their declared mem...
-
...you could run the obfuscated Android SoC driver shit, or even outright proprietary blobs, without even having to care what they do.
- 2 more replies
New conversation -
-
-
I wish so much Linux had QNX's lightweight messaging system. Could make drivers so nice.
-
Yeah, I really don't care what the mechanism is or what the performance aspects are as long as it works, though.
-
Most people's loads are NOT hw-access-bound but cpu-, memory-, and/or gpu-bound.
-
Oh certainly. I want the mechanism to work for network card drivers too.
-
If your loads are network-card-bound, then you need some more attention to isolating the driver in a way that doesn't hurt your perf.
-
But that only affects datacenter type users, not mobile, laptop, desktop, small server users.
-
So everyone else is suffering miserable security model for the sake of enterprise/datacenter network performance needs...
-
Oh certainly. We're over optimized for the wrong users in many cases.
End of conversation
New conversation -
-
-
It would, however, help if hardware interfaces were designed to make that straightforward.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.