Browse Source

MT#55283 document io-uring option

Change-Id: I84da22770f80c54969adb59ee36da2bed27448ea
pull/1826/head
Richard Fuchs 2 years ago
parent
commit
9bce3a0077
2 changed files with 18 additions and 0 deletions
  1. +17
    -0
      docs/rtpengine.md
  2. +1
    -0
      etc/rtpengine.conf

+ 17
- 0
docs/rtpengine.md View File

@ -1148,6 +1148,23 @@ call to inject-DTMF won't be sent to __\-\-dtmf-log-dest=__ or __\-\-listen-tcp-
thus maintaining the order of the packets. Might help when having issues with
DTMF packets (RFC 2833).
- __\-\-io-uring__
Enable **experimental** support for `io_uring`. Requires Linux kernel 6.0
or later.
When enabled, instead of the usual polling mechanism each worker thread
will set up its own `io_uring` and use it for polling, as well as directly
sending and receiving certain network data. In particular userspace media
data is sent and received directly via `io_uring`.
_NOTE: As of the time of writing, worker threads sleeping in an `io_uring`
poll are attributed to the host system as _I/O wait_ CPU usage, with up to
99% CPU time spent in _I/O wait_ (depending on the number of worker
threads), but without being attributed to any process or thread. This is
not actual CPU usage but rather indicates time spent waiting for a network
event, and so should be considered the same as idle CPU time._
- __\-\-dtls-cert-cipher=prime256v1__\|__RSA__
Choose the type of key to use for the signature used by the self-signed


+ 1
- 0
etc/rtpengine.conf View File

@ -136,6 +136,7 @@ recording-method = proc
# mos = CQ
# poller-per-thread = false
# io-uring = false
# socket-cpu-affinity = -1
# rtcp-interval = 5000


Loading…
Cancel
Save