It would seem to me that using activate_task() in __migrate_task() in
lieu of __activate_task() has two undesirable consequences: 1)
recalculating and resetting prio and 2) resetting the time stamp. The
fact that the time stamp is adjusted for the change of run queue just
before activate_task() is called reinforces my suspicion that these
consequences are unintended.
Is there a reason for using activate_task() that I can't see?
Peter
--
Peter Williams [email protected]
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
