This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: [PATCH] [RFC] Credit2 scheduler prototype

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] [RFC] Credit2 scheduler prototype
From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
Date: Tue, 8 Dec 2009 14:48:44 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 08 Dec 2009 06:49:07 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=rDhqlLu577dHHP4B3fdmtpBZ1k2ve/wkB/q3cSGgvXw=; b=okaCUBWoUIBJ/be7lKK2uWxocwrKaVS65AUiV1DbzcSc/uItwcGUfn2J8i9EhjragQ jaAbM32zHyNuwR1+E4aCUC1TLx0ccwANVxeZWKXWOh1rpGOqIiSgVff7v6HHAkv43y7p bfCqN435u3AL4gQoidwP3GFL8juGctREzPJpY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=VALtYBQZHiKWx+aQFdnoeg6NWhfYeZVqKRk5buR5YhNFbM1ZvBMtz6GKDVIQtzpzDV g3cXRfQMD35OVC80IC9vQ9L3MElZmTiASxUqtkNbUadu44XojqDDPs9aNnRPsyRtkQ5Z 43yhDUiE6WJKJg2mZIjqn5VQJ+ZbUh/VF5tSs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C742EFC4.3C2C%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <de76405a0912070902p4afe2128t1599573653accf26@xxxxxxxxxxxxxx> <C742EFC4.3C2C%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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. :-)


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


On Mon, Dec 7, 2009 at 5:45 PM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
> On 07/12/2009 17:02, "George Dunlap" <George.Dunlap@xxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>