3 ms·
100 syscalls for a microkernel sounds like a lot. Is that standard? I thought the reasoning behind microkernels was for dispatching to userland processes to han
by chc4 9y ago
100 syscalls for a microkernel sounds like a lot. Is that standard? I thought the reasoning behind microkernels was for dispatching to userland processes to handle things instead of needing a lot of syscalls.
- lobster_johnson 9y agoHere's a list [1]. I count 131 syscalls. Most of them are related to hardware (PCI, timers, CPU, framebuffer), a bunch are related to logging/tracing. There's a small set that address kernel "objects" (processes, ports etc.). [1] https://github.com/fuchsia-mirror/zircon/blob/master/system/public/zircon/syscalls.sysgen https://github.com/fuchsia-mirror/zircon/blob/master/system/...
- swetland 9y agoSome more detailed info here: http://zircon.fyi/syscalls.md http://zircon.fyi/syscalls.md http://zircon.fyi/concepts.md http://zircon.fyi/concepts.md The PCI syscalls and a lot of the other DDK scaffolding stuff will be going away in time (and are not accessible to general userspace processes). I'm hopeful that we'll hit 1.0 with fewer than 100 public syscalls and hopefully not many more than 100 total.