All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "G.raud" <graud-KK0ffGbhmjU@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: select.2: s/minimum/maximum/
Date: Wed, 04 Sep 2013 10:40:50 +0200	[thread overview]
Message-ID: <5226F212.6000709@gmail.com> (raw)
In-Reply-To: <20130823151009.30030-KK0ffGbhmjU@public.gmane.org>

>> One could I suppose reword something like this:
>>
>>        The timeout argument specifies the interval that select()  should
>>        block  waiting for a file descriptor to become ready.  In effect,
>>        timeout specifies a minimum interval: the timeout will be rounded
>>        up  to the system clock granularity, and kernel scheduling delays
>>        mean that the blocking interval may overrun by  a  small  amount.
>>
>> But I'm not sure that that is really much of an improvement.
> 
> I see it as a huge improvement because it does not reverse the meaning
> of timeout.

Okay -- I've the simpler patch below.

Cheers,

Michael

--- a/man2/select.2
+++ b/man2/select.2
@@ -159,12 +159,12 @@ is the highest-numbered file descriptor in any of the three sets, plus 1.
 .PP
 The
 .I timeout
-argument specifies the minimum interval that
+argument specifies the interval that
 .BR select ()
 should block waiting for a file descriptor to become ready.
-(This interval will be rounded up to the system clock granularity,
+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.)
+may overrun by a small amount.
 If both fields of the
 .I timeval
 structure are zero, then



--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2013-09-04  8:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-23 15:10 select.2: s/minimum/maximum/ G.raud
     [not found] ` <20130823151009.30030-KK0ffGbhmjU@public.gmane.org>
2013-09-04  8:40   ` Michael Kerrisk (man-pages) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-08-22 15:38 G.raud
     [not found] ` <20130822153850.29990-KK0ffGbhmjU@public.gmane.org>
2013-08-23  8:51   ` Michael Kerrisk (man-pages)
2013-08-19 23:00 G.raud
     [not found] ` <20130819230019.190010-KK0ffGbhmjU@public.gmane.org>
2013-08-22  7:22   ` Michael Kerrisk (man-pages)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5226F212.6000709@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=graud-KK0ffGbhmjU@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.