[haiku-development] Re: The new locking primitives and boosting -- I need some guidance here :)
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 25 Jun 2008 12:49:45 +0200 CEST
"André Braga" <meianoite@xxxxxxxxx> wrote:
> And since we touched this topic, the priority levels on Haiku will
> probably need to be tweaked in order to implement multiuser
> support...
Huh? At least I don't see any connection here.
> > Thread priorities are fairly well
> > understood and deployed in BeOS land. I've only ever come across
> > one
> > project where there was a misunderstanding and a 3D renderer was
> > given a
> > high priority.
> I'm not disputing this at all. What I am saying, instead, is that
> sometimes the same thread might behave in a way, and in the next
> moment behave completely differently, and any given priority level
> might not capture this subtlety.
While that is true, if it has any undesirable effect it is most likely
a design problem of your software :-)
In general, if more than onev thread may have their share of CPU time
now, the one with the higher priority should win and be scheduled
first.
Unless you can show that this isn't enough to provide a good experience
(with an otherwise fair scheduler), I don't see why you should spend
much time on it. IOW just get the scheduler integrated first, before
thinking about how to make eventually it better -- these things are
much better done with a working example at hand.
Bye,
Axel.
Other related posts:
