In message <5.1.0.14.2.20030115075248.02669e88 at falcon.si.com> you wrote: > > The idea is that your processing task waits on a semaphore: when someone > has something for it to do, they release (post/signal) the semaphore which > unblocks the processing task. This allows the processing task to (a) not > consume processor resources when it doesn't have anything to do and (b) > start up immediately when there is something to do (as opposed to having to > wait for its slice of processor time).
Since serial and network I/O are involved, the "semaphore" might be as simple as a select(), of course. But that does not fix any scheduling latencies. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de Work 8 hours, sleep 8 hours; but not the same 8 hours. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
