Fix documentation to say UV_LOOP_USE_IO_URING_SQPOLL instead of the internal UV_LOOP_ENABLE_IO_URING_SQPOLL name

This commit is contained in:
Poul T. Lomholt 2025-05-14 17:39:06 -07:00
parent 8d4218dcd7
commit 1602315656
2 changed files with 3 additions and 3 deletions

View File

@ -19,7 +19,7 @@ observable behavior. Libuv reverts to using its threadpool when the necessary
kernel features are unavailable or unsuitable. Starting with libuv v1.49.0 this
behavior was reverted and Libuv on Linux by default will be using the threadpool
again. In order to enable io_uring the :c:type:`uv_loop_t` instance must be
configured with the :c:type:`UV_LOOP_ENABLE_IO_URING_SQPOLL` option.
configured with the :c:type:`UV_LOOP_USE_IO_URING_SQPOLL` option.
.. note::
On Windows `uv_fs_*` functions use utf-8 encoding.

View File

@ -86,12 +86,12 @@ API
This option is necessary to use :c:func:`uv_metrics_idle_time`.
- UV_LOOP_ENABLE_IO_URING_SQPOLL: Enable SQPOLL io_uring instance to handle
- UV_LOOP_USE_IO_URING_SQPOLL: Enable SQPOLL io_uring instance to handle
asynchronous file system operations.
.. versionchanged:: 1.39.0 added the UV_METRICS_IDLE_TIME option.
.. versionchanged:: 1.49.0 added the UV_LOOP_ENABLE_IO_URING_SQPOLL option.
.. versionchanged:: 1.49.0 added the UV_LOOP_USE_IO_URING_SQPOLL option.
.. c:function:: int uv_loop_close(uv_loop_t* loop)