Hi! On 12:15 Fri 06 Mar , microbit@xxxxxxxxxxxxxxxxxxxxxx wrote: ... > In this case it's common to use co-operative scheduling. This means that > when a task does not need further execution, it must relinquish control > back to the scheduler. I personally find this a real pig to program like > that, but it does allow very compact targets (altough this is more for the > embedded world) Just because you do not want to preempt running kernel code, it does not mean that you have to do co-operative scheduling. You can still preempt user space code. You can see the "big kernel lock" for more details (but do *not* use it in new code - people try to get rid of it). -Michi -- programing a layer 3+4 network protocol for mesh networks see http://michaelblizek.twilightparadox.com -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
