2 ms·
>What's your criteria for "really asynchronous" One example might be that related operations, like stat(), opendir(), readdir(), getpeername(), and so on...rem
by tyingq 7y ago
>What's your criteria for "really asynchronous"
One example might be that related operations, like stat(), opendir(), readdir(), getpeername(), and so on...remain synchronous. And that async functionality is mostly a bolt-on to very established things, file descriptors, berkeley sockets etc.
Also, every improvement is a pretty big patchset with code to ensure the traditional synchronous operations don't get unintended side effects.
Just generally the idea that a "clean start", non-POSIX bound OS might design things differently, I imagine. Google's Fuchsia seems to hit some middle ground, where async is more foundational, for example.
I don't think that observation detracts from the improvements.
- chriswarbo 7y ago> Just generally the idea that a "clean start", non-POSIX bound OS might design things differently, I imagine. Google's Fuchsia seems to hit some middle ground, where async is more foundational, for example. Microsoft's (research, discontinued) Midori OS was heavily async: http://joeduffyblog.com/2015/11/19/asynchronous-everything http://joeduffyblog.com/2015/11/19/asynchronous-everything
- tyingq 7y agoThat's exactly where I was going. Critisim of Linux async shouldn't be discouraged because of inherent limitations. That would hample innovation. I wouldn't be surprised by a new web server, API gateway, load balancer, etc, that mandated "forget about POSIX, adhere to this". The whole cloud abstraction movement seems to enable it.
- yxhuvud 7y agostatx exist as opcode, so stat through the ring is a solved problem. Directory operations are not implemented yet, but I'd be surprised if they don't arrive, sooner than later.
- tyingq 7y agoI view that as confirmation of the GP observation. Async is an afterthought for Xnix.