Re: Scheduler: Spinning until tasks are STOPPED

[Yuly Finkelberg]

Nick,

> You're doing this in the *kernel*? It sounds like it should be done
> in userspace or done a different way (ie. not with 50 tasks).

These are tasks that are running in the kernel on behalf of a new system call.  

> And using signals and spinning on yield for synchronisation and
> process control in the kernel like this is fairly crazy.

The problem appears to be not with the process that is
spinning/yielding, but rather the one process which gets stuck.  It is
charged almost all the system time.  I agree that it's not pretty
though...

> Can't you use a semaphore or something?

There is noone to call up() when a process is actually stopped.

If you have any ideas as to what can be happening or a better way to
accomplish this (in the kernel), I'd appreciate hearing it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/