<html><body>
<p><tt>cbe-oss-dev-bounces+lukebrowning=us.ibm.com@ozlabs.org wrote on 02/24/2007 04:38:19 AM:<br>
<br>
> On Thu, Feb 22, 2007 at 09:25:04PM -0300, Luke Browning wrote:<br>
> > You might also want to retest the priority fields under the ctx lock to<br>
> > make ensure that the priorities haven't changed. The code above uses the<br>
> > runqueue lock, which doesn't protect these fields, right?<br>
> <br>
> Currently these fields are never updated after the context creation,<br>
> so the lock is not needed. But once we're doing dynamic timeslicing<br>
> we will need to introduce locking here.<br>
> <br>
<br>
Hmm, the application should be able to change the priority and policy of a ctx, if it </tt><br>
<tt>changes the priority of the controlling entity (ie. kernel thread or process). The</tt><br>
<tt>scheduling parameters should be able to be changed dynamically.</tt><br>
<br>
<tt>Luke</tt><br>
</body></html>