> Isn't the timer also used for the PI loop? Or has much of that design been
The timer goes off each second, and then calls various routines to see if they
have any work to do. Many of those routines decrement a counter each time they
get called and then do the real work (such as send a request) when the counter
It would be possible to peek ahead and see when the next time any work will
actually get done and set the timer that far ahead.
Most of the PI type work is in response to reply packets coming back. The
timer triggers sending the request that makes the reply.
These are my opinions. I hate spam.
devel mailing list