Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Getting that right at the implementation level is quite hard; it also requires support at the OS level that isn't always there (e.g. interrupting a blocking system call).


Then avoid blocking system calls.

When you can't, defer them to a thread that can be ignored.


That's a huge footgun in an environment where blocking calls are the default way to get almost anything done, and some calls cannot be made non-blocking.


True, but we don't have much trouble with it though. We don't directly call syscalls but use our own wrappers that take care of this for us.


Sorry for the late reply, but I just saw this reply. Can you share who "we" are? I'm always interested in new practical systems for concurrency.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: