Re: Re: [PATCH] [RFC] Credit2 scheduler prototype

[George Dunlap <George.Dunlap@eu.citrix.com>]

My main concern is that sharing the runqueue between cores requires
some changes to the core context switch code. The kinks aren't 100%
worked out yet, so there's a risk that there will be an impact on the
correctness of the credit1 scheduler.

If you want to go that route, we should probably talk about the
changes we want to the context switch path first, and check that in as
a separate patch, before checking in the core scheduler code.

Or we could just check it in and sort it out as things go, since this
is -unstable. :-)

Thoughts?

Either way I'll write up an e-mail describing some of the scheduler
path changes I'd like to see.

 -George



On Mon, Dec 7, 2009 at 5:45 PM, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
> On 07/12/2009 17:02, "George Dunlap" <George.Dunlap@eu.citrix.com> wrote:
>
>> Keir (and everyone), I think at this point it would be a good idea to
>> start a credit2 development branch in ext/ so we can keep a revision
>> history.  Thoughts?
>
> Sounds like a reasonable idea, if you don't think it suitable just to check
> into mainline as the non-default scheduler.
>
>  -- Keir
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>