News for hackers. Stuff that matters.
Re:Coroutines and Fibers: Why and When by avdicius on Friday January 15, 2016 @10:18PM (#10914056)
Upon return from a non-blocking I/O call the request is either failed or succeeded. Upon return from an async I/O call the request might additionally be in progress thus the fiber is required to wait for its completion. This case has little practical difference from a thread pool. Except with a thread pool it is the worker thread that notifies the fiber scheduler on I/O completion. With async I/O it is the kernel that notifies the application and then the application (from a signal handler or from an auxiliary thread) should propagate the notification to the fiber scheduler.

There are no comments on this comment yet.