If you use kqueue (), should you set O_NONBLOCK to your file descriptors? In other words, kqueue () ensures that the next I / O operation in the finished file descriptor will not be blocked, regardless of whether O_NONBLOCK is set?
If you use kqueue (), should I set O_NONBLOCK to file descriptors?
Nope.
In other words, kqueue () ensures that the next I / O operation in the finished file descriptor will not be blocked, regardless of whether O_NONBLOCK is set?
Yes.
. , . read() return -1 errno EWOULDBLOCK. EWOULDBLOCK , kqueue , () (, , ) .
Source: https://habr.com/ru/post/1693630/More articles:How to write tests with parameter parameters for values in a non-stationary container? - c ++Does ConfigureAwait (false) do anything - c #Adding a new column using gregexpr - rPoor performance with large write operations on O_NONBLOCK fifo in mac os - ioHow to write shebang when using minor functions - pythonseveral operations in the list of complex objects with lambda - javaHow to wrap a C ++ object using pure Python extension API (python3)? - c ++Can caching DNS servers update the cache asynchronously? - low-latencyПочему window.open не блокируется на setTimeout <= 1000 мс? - javascriptPHP loop and $ multidimensional array return key - arraysAll Articles