On Mon, 24 Jan 2000, Matthew Dillon wrote:
> :
> :The "maximum interval to wait for the selection to complete" isn't
> :really the maximum, but more like the lower bounds of the time to
> :wait for the selection.
> :
> :Dan Eischen
> :[EMAIL PROTECTED]
>
> It's definitely a maximum, because select() can return much sooner if
> one of the I/O events being waited on occurs.
It's not a maximum if you round up to the nearest clock tick.
> If you call it a minimum
> you imply that select() will not return until at least the specified
> amount of time elapses, which is incorrect. Just because it may go
> slightly over the specified time when no I/O events are pending does not
> change anything -- FreeBSD is not a hard-realtime system and programmers
> understand that. If anyone were to actually get confused by this, they
> have to go back to school.
I know all this, but I still prefer Solaris' wording over what we
have. If someone is going to change the man page for this, then
I suggest we do it in a way that is more clear. "system activity"
doesn't seem to me to cover rounding up to the nearest clock tick.
I'm happy with leaving the man page as it is also.
Dan Eischen
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
