angelo_f at bigpond.com
Sun Feb 24 03:03:51 UTC 2002
You are right. Sending the event if the queue was not originally empty
when the ISR came is not necessary. I was already looping the task until
the queue was empty; I was, however, sending the event regardless --
which is actually wasting CPU cycles. Thanks for the tip? I'll see what
I can get the interval down to by not sending an unnecessary event.
Chris Johns wrote:
>Angelo Fraietta wrote:
>>Within the ISR I am doing the following:
>>Reading a 16 bit word from an I/O address
>>Decoding and adding that word onto a queue that is emptied out by a
>>Checking a second queue for data that needs to be transmitted
>>Transmitting a word to the I/O card.
>>Setting an event that causes the running task to empty the queue.
>I would only send the event if the queue is empty and have the task loop
>until the queue is empty.
PO Box 859
Hamilton NSW 2303
There are those who seek knowledge for the sake of knowledge - that is CURIOSITY
There are those who seek knowledge to be known by others - that is VANITY
There are those who seek knowledge in order to serve - that is LOVE
Bernard of Clairvaux (1090 - 1153)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users