Re:How the Windows Subsystem for Linux Redirects Syscalls
by binarycrusader on Thursday June 09, 2016 @09:03PM
(#11873570)
Your rephrasing still doesn't matter, Solaris event ports are not signal-based.
My understanding is that Solaris event ports were intended to offer equivalent functionality to Windows' I/O completion ports, so this should not be surprising.
Solaris also has its own native async I/O API in addition to supporting POSIX async.
My understanding is that Solaris event ports were intended to offer equivalent functionality to Windows' I/O completion ports, so this should not be surprising.
Solaris also has its own native async I/O API in addition to supporting POSIX async.