> Both of these methods have problems, especially with the proposed
> preemptions changes. The first case causes the thread to run with the
> BKL for the whole time. This means that any other task that wants the
> BKL will be blocked. Surly the needed protections don't require this.
The BKL is dropped on rescheduling of that task. Its an enforcement of the
old unix guarantees against other code making the same assumptions. Its also
the standard 2.4 locking for several things still
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
