From e92e5cbc9c42a7f926eb4b25fdf6e52ec9d2fa4c Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Mon, 28 Apr 2025 08:44:56 +0000 Subject: Update docs to latest posix version Signed-off-by: Laurent Bercot --- doc/libstddjb/iopause.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'doc/libstddjb/iopause.html') diff --git a/doc/libstddjb/iopause.html b/doc/libstddjb/iopause.html index 3fbe5b8..1c240cf 100644 --- a/doc/libstddjb/iopause.html +++ b/doc/libstddjb/iopause.html @@ -30,9 +30,9 @@ and implemented in the libskarnet.a or libskarnet.so library.

iopause is the skalibs API for event loop selection. It's a wrapper around the system's ppoll() or -poll() +poll() (if available) or -select() +select() (if neither ppoll() nor poll() is available) function. It works around some system-dependent quirks; also it works with absolute dates instead of timeouts. This is a good thing: @@ -49,7 +49,7 @@ skalibs implementation is subtly different.

An iopause_fd structure is similar to a -struct pollfd +struct pollfd structure, and must be filled the same way. Usually, the user declares an array of iopause_fd and fills it, one element per descriptor to select on. If x is an iopause_fd: @@ -183,9 +183,9 @@ instead if they configure skalibs with the --enable-iopause-select opti

-poll() +poll() has a more comfortable API than -select(), +select(), but its maximum precision is 1 millisecond, which might not be enough for some applications; using select() instead incurs some CPU overhead for the API conversion, but has a 1 microsecond precision. -- cgit v1.3.1