Writing an OS in Rust: Returning from Exceptions

Re:Writing an OS in Rust: Returning from Exceptions by bluejekyll on Wednesday September 21, 2016 @11:37PM (#12554135)

> Why aren't there reactive operating systems (as in OS with reactive API)

This is something that's been interesting me lately. I've been working with the excellent futures and tokio libraries, and I've wondered what would it be like if that was the primitive for all OS interactions?

Basically, imagine a message passing system like Mach, but where the fundamental messages are all futures based. There might be some interesting things possible without holding locks in the kernel.

[ Parent | on HN ]

Re:Writing an OS in Rust: Returning from Exceptions by phil-opp on Thursday September 22, 2016 @10:01AM (#12556846)

I definitely plan to integrate the futures library in the kernel somehow. We just need some asynchronous things and threads first :).

[ Parent | on HN ]

Re:Writing an OS in Rust: Returning from Exceptions by bluejekyll on Thursday September 22, 2016 @11:18AM (#12557399)

cool! Do you have an overarching design your working off of? Or still too low level?

[ Parent | on HN ]

Re:Writing an OS in Rust: Returning from Exceptions by phil-opp on Saturday September 24, 2016 @06:48AM (#12570401)

I have some vague ideas for the next posts, but no overarching design. At our current level, there aren't many design choices anyway. It will get much more intesting when we create a threading/concurrency model in the future.

[ Parent | on HN ]