[Live-devel] About the tv_timeToDelay param in the select() function

zhi sun zhisun.tech at gmail.com
Sun Dec 28 20:12:48 PST 2008


Hi Ross,

I have another question about the tv_timeToDelay param in the select()
function, in BasicTaskScheduler class.

By default, I notified the timeout value is 0, that means the select() never
stops for waiting an available signals (connect/read socket, read file).

I am wondering why not to set the timeout to NULL, to let the select()
drivern by the signals. It takes less CPU cycle.

On linux, I think it is OK to set the timeout to NULL.

On windows, the select() cann't detect the read file signal, so can only
read the file once, and be hold there until getting RTCP request from the
client.

Is it necessary to set the timeout value depends on different OS.

On our embeded device, there is no both the build-in select() function
support. So the performance is very poor. Ross, could you please point me an
correct direction to write an custom select() function?

The OS is uCOS, I cannot make change to it (duc to licence). But I may be
able to make change the low BIOS level (on which, the uCOS runs). I want to
see if it is possible to write an my own select() function based on the BIOS
(which interacts with the hardware board directly), or is there a better
way. I have notified that there are some similar posts, but the performance
is criticle for our embeded device, an custom select() function based on the
application level may not address my issue.

Thanks for any suggestion!

Thanks,
-kevin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20081229/769da3ff/attachment.html>


More information about the live-devel mailing list