LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

recvmmsg.2: Clarify that 'timeout' is a *minimum* interval 

Make it clear that 'timeout' interval will be rounded up to the
system clock granularity, and may overrun because of kernel
scheduling delays.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2012-05-02 08:09:03 +12:00
parent 95b803548b
commit 3a1876bd71
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
man2/recvmmsg.2
View File

@ -23,7 +23,7 @@
.\"
.\" FIXME: This page could be improved with an example program.
.\"
.TH RECVMMSG 2 2011-10-04 "Linux" "Linux Programmer's Manual"
.TH RECVMMSG 2 2012-05-02 "Linux" "Linux Programmer's Manual"
.SH NAME
recvmmsg \- receive multiple messages on a socket
.SH SYNOPSIS
@ -107,6 +107,9 @@ argument points to a
(see
.BR clock_gettime (2))
defining a timeout (seconds plus nanoseconds) for the receive operation.
(This interval will be rounded up to the system clock granularity,
and kernel scheduling delays mean that the blocking interval
may overrun by a small amount.)
If
.I timeout
is