bryancall commented on code in PR #9630:
URL: https://github.com/apache/trafficserver/pull/9630#discussion_r1187902180
##########
doc/admin-guide/files/records.yaml.en.rst:
##########
@@ -5196,3 +5196,46 @@ Sockets
.. _Traffic Shaping:
https://cwiki.apache.org/confluence/display/TS/Traffic+Shaping
+
+IO_URING
+========
+
+.. ts:cv:: CONFIG proxy.config.io_uring.entries INT 32
+
+ Specify the number of entries in each io_uring. There will be on io_uring
instance per thread that uses io_uring
+ for IO. This parameter is passed to io_uring_queue_init.
+
+.. ts:cv:: CONFIG proxy.config.io_uring.sq_poll_ms INT 0
+
+ If this value is >0 then use submit queue polling mode. The value will be
used to specifiy the sq_thread_idle parameter
+ to io_uring setup. More information about submit queue polling mode can be
found here: https://unixism.net/loti/tutorial/sq_poll.html
+
+.. ts:cv:: CONFIG proxy.config.io_uring.attach_wq INT 0
+
+ Set this to 1 if you want io_uring to re-use the same worker queue backend
for each thread.
+
+.. ts:cv:: CONFIG proxy.config.io_uring.wq_workers_bounded INT 0
+.. ts:cv:: CONFIG proxy.config.io_uring.wq_workers_unbounded INT 0
+
+ These settings configured the number of threads for the io_uring worker
queue backend. See the manpage for
+ io_uring_register_iowq_max_workers for more information.
+
+AIO
+===
+
+.. ts:cv:: CONFIG proxy.config.aio.force_aio STRING NULL
+
+ (Only if io_uring is enabled in the build)
+ Normally, ATS will detect if io_uring can be used for async disk IO. Using
this config item, the AIO mode
+ can instead be specified. The value can be one of:
+
+ ============
======================================================================
+ Value Description
+ ============
======================================================================
+ ``NULL`` Use the default detection logic
Review Comment:
Why have a NULL setting in the documentation? Is someone supposed to set it
to NULL to get auto detection?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
