Marcus Spangenberg wrote:
To the original poster, I'd suggest starting with an
existing class
(like FX) and modifying it as needed.  Or just write
a user level
scheduler that modifies FX priorities and time quanta
using priocntl
(the easiest solution if the timing constraints
aren't that tight).

Andy

Will probably modify an existing scheduler since the plan is not to change the 
scheduling policy but to make the process scheduler power aware by scheduling 
processes on processors in the most power efficient way and shutting down cores 
/ other parts of the processor die on a SMP/CMP architecture when unused. 
Therefore kernel mode would be the way to go in order to get access to hardware.

The scheduling classes implement policy that deals mainly with thread priorities. The dispatcher code (in usr/src/uts/common/disp/disp.c), deals more with selecting where (on which CPUs) threads should be scheduled to run...so given what you want to do, this is probably where you would want to have your sights set.

Thanks,
-Eric


_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code

Reply via email to