Code review, new scheduler:
alexander.kjeldaas at gmail.com
Thu Jan 31 11:22:00 CET 2013
On Thu, Jan 31, 2013 at 11:06 AM, Edward Z. Yang <ezyang at mit.edu> wrote:
> Excerpts from Alexander Kjeldaas's message of Thu Jan 31 01:57:17 -0800
> > Found it, it's still there:
> > Note that these are *timers*. Timers are often set up and then canceled.
> > As you see, the buckets are not sorted, timers are just put at the end
> > a list, and the lists are even hard-coded so they are more general than
> > log2 buckets.
> > The point of this is to partially sort the timers as they get closer to
> > expiration. Thus you don't pay the full sorting cost if the timer is
> > modified before it expires.
> Ah, I see. GHC threads are very rarely canceled, so I don't think we would
> see much benefit here.
You are probably right. I can think of priority inversion with rapidly
changing priorities as a possible use-case then.
Anyways, keep up the good work!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ghc-devs