Upon further reflection, I think it does not make sense for application programmer to control CPU distribution down to the ticks.
This would over-specify the scheduling requirements, which often are quite lax.
Presence of multiple physical processors makes the situation even worse.
What probably makes sense is to allow the application developer to explicitly track the separate computation parts, assigning to them various properties, and enabling two-way reflective link between the programmer and the real scheduler.
Think of this as a task management system, e.g., Jira.
Persons acting in one role can create tasks, manage their dependencies, deadlines, estimates and priorities, while persons in another role execute the project making sure the tasks are completed at a satisfactory time.
The first role is like one for the application developer, the second one is for the scheduler of the language's runtime.
Subscribe to:
Post Comments (Atom)
2 comments:
Hey! I know this is kinda off topic but I'd figured I'd ask.
Would you be interested in trading links or maybe guest authoring a blog article or vice-versa?
My blog addresses a lot of the same subjects as yours and I
think we could greatly benefit from each other. If you're interested feel free to send me an e-mail. I look forward to hearing from you! Excellent blog by the way!
my website :: bmi index chart
wonderful issues altogether, you simply won a brand new reader.
What would you suggest in regards to your put up that you made a few days ago?
Any sure?
My blog post - London outcall massage - trachome.com -
Post a Comment