RE: [MI400] what is a reasonable socket select() wait time?

["Hall, Philip" <phall@xxxxxxxx>]

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
> The API reference for the socket select() wait time parameter says,
>
> "A time to wait of 0 is allowed; this returns immediately
> with the current
> status of the sockets."
>
> What is this "current status" that gets returned?

The current status is the fd_set(s) - and whether and fd's are read for
read/writing. For example if you're off doing something else, before you hit
your select(), you can use a wait time of 0 to immediatly determine if
anything needs doing (read/write to/from the sockets), before settling down
to a more 'normal' wait time.


> Question 2:
>
> Will a non-zero select() wait time value slow down an
> application, if our
> actual receive data length is less than our default TCP
> receive buffer size
> SO_RCVBUF (which is 8192 bytes), and our allocated receive
> data length is
> greater than 8192, and no multiplex I/O occurs?

The underlying code for select() will still have to do some work to
determine which fd_set elements to set, modify your fd_set(s) and return
them, I would have thought.

--phil