From f3d5157564992f1ef9f390b3ce0c7d3706ba0f19 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Sun, 4 Oct 2020 01:06:16 +0000 Subject: doc: fix URLs --- doc/libstddjb/iopause.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'doc/libstddjb/iopause.html') diff --git a/doc/libstddjb/iopause.html b/doc/libstddjb/iopause.html index 0ddaade..6b35416 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() n or 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: @@ -41,7 +41,7 @@ see below.

iopause is a derived work from Dan J. Bernstein's -iopause library, but the +iopause library, but the skalibs implementation is subtly different.

@@ -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,13 +183,13 @@ 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. -ppoll() gets the best of +ppoll() gets the best of both worlds with the same interface model as poll() and a 1 nanosecond precision, which is why skalibs always uses it when available.

-- cgit v1.2.3