| ??? 04/24/03 21:04 Read: times |
#44167 - RE: function-queu- scheduling architecture Responding to: ???'s previous message |
The functions address would be placed in the queue (This is done inside a interrupt).
If you do this, make darn sure you disable interrupts while working the queue in the main code. It's a improvemnet over round robbin interrupt coding Not necessarily, and it add a layer of confusion. I insist that any routine called from the round robin determine ASAP if it has anything to do (that may require setting - in the above mentioned interrupt - and testing a flag) and, if not, get the h... out of there. This test is so much faster than loading the first routine in the stack, pulling the stack one down and then executing. To even speed it up more, the test can be done in the robin (I do not like that) and the call bypassed. If you work fast from the robin you should not, and from the stack you can not, pass parametres to the top layer routines. Erik |
| Topic | Author | Date |
| function-queu- scheduling architecture | 01/01/70 00:00 | |
| RE: function-queu- scheduling architecture | 01/01/70 00:00 | |
| RE: function-queu- scheduling architecture | 01/01/70 00:00 | |
RE: function-queu- scheduling architecture | 01/01/70 00:00 |



