Hi...
I think I made mistake...
The second question is, why the cond_resched() have PREEMPT_ACTIVE
flag set before calling schedule()? The comments seems to say it is to
prevent a second (recursive?) call of cond_resched(), but I can not
see any recursive call in the source code. Did I miss anything?
I see comments like this:
*//*/*/* The BKS might be reacquired before we have dropped/*
*/ PREEMPT_ACTIVE, which could trigger a second/*
*/* cond_resched() call.*//*
I don't know what BKS is, maybe it means BKL. In that case, without
looking into the actual codes, I guess while BKL is reacquired, it
implicitly call cond_resched(). That's the 2nd "hidden" cond_resched. I
hope I do it correctly this time.
regards,
Mulyadi
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
