[Asio] Propose optimization patch for QNX OS.
Hello, By default on QNX OS the select_reactor class is used, which uses the POSIX select() to wait for I/O and write to a pipe to interrupt the wait. Neither select() nor pipes are efficient on QNX OS. We propose to introduce new ionotify_reactor class for QNX OS, which uses ionotify() and pulses instead of select() and pipes. If you are interested in this patch please let me know how to proceed with it: - what repo and branch should I use for this patch? - what is mandatory test set should be done for this patch? - what documentation should be updated to reflect this patch? Thanks, Alex Steshkin ---------------------------------------------------------------------- This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
On 9/2/21 8:10 PM, Alex Steshkin via Boost wrote:
Hello,
By default on QNX OS the select_reactor class is used, which uses the POSIX select() to wait for I/O and write to a pipe to interrupt the wait. Neither select() nor pipes are efficient on QNX OS. We propose to introduce new ionotify_reactor class for QNX OS, which uses ionotify() and pulses instead of select() and pipes. If you are interested in this patch please let me know how to proceed with it: - what repo and branch should I use for this patch? - what is mandatory test set should be done for this patch? - what documentation should be updated to reflect this patch?
Main ASIO development happens here: https://github.com/chriskohlhoff/asio/ Boost.ASIO is produced from that source code automatically. You probably want to propose your patch there.
participants (2)
-
Alex Steshkin
-
Andrey Semashev