News for hackers. Stuff that matters.
Re:Snap: A Microkernel Approach to Host Networking by AlphaSite on Monday October 28, 2019 @03:43AM (#21374998)
Another point is that macOS and iOS are moving towards a user space driver stack and away from Kernel space.
Re:Snap: A Microkernel Approach to Host Networking by snvzz on Monday October 28, 2019 @03:59AM (#21375064)
Because, save few exceptions (e.g. timers, early debug serial...) running drivers in supervisor mode isn't very smart.

Drivers tend to have high bug density, and supervisor mode means high potential for damage.

Much can be mitigated by running drivers in userspace[0][1], especially with some IOMMU help.

[0] https://www.cs.vu.nl/~herbertb/papers/minix3_dsn09.pdf

[1] https://wiki.minix3.org/doku.php?id=www:documentation:reliab...

Re:Snap: A Microkernel Approach to Host Networking by pjmlp on Monday October 28, 2019 @04:07AM (#21375092)
Android and Windows as well.
Re:Snap: A Microkernel Approach to Host Networking by panpanna on Monday October 28, 2019 @08:27AM (#21376233)
Linux has been moving towards hybrid drivers for certain components for a while now.

I think you can run large parts of the filesystem and network stack in user-land now.

Re:Snap: A Microkernel Approach to Host Networking by pjmlp on Monday October 28, 2019 @08:41AM (#21376313)
There is a big difference is that the other OSes are doing it no matter how many pitchforks come into their way, while with Linux you need to find a security conscious distribution.
Re:Snap: A Microkernel Approach to Host Networking by Matthias247 on Monday October 28, 2019 @11:38AM (#21377908)
I think it’s hard to say that without knowing what’s going on in that companies and how many internal disagreements had been there.

And even if Apple now talks about user-Mode drivers - do we even know what percentage they aim for?

Re:Snap: A Microkernel Approach to Host Networking by pjmlp on Monday October 28, 2019 @12:21PM (#21378329)
Yes we do, as they presented at WWDC, all of them.

They are following a two release steps, in release N, the user space drivers for a specific class get introduced and the respective kernel APIs are automatically deprecated. In release N + 1, those deprecated APIs will be removed.