WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] credit based scheduler

To: "Emmanuel Ackaouy" <ack@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] credit based scheduler
From: "Molle Bestefich" <molle.bestefich@xxxxxxxxx>
Date: Thu, 22 Jun 2006 12:26:02 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 22 Jun 2006 03:26:23 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=SvnJua7DrpyLo0ZiWUfplNvJ/c61/EUjvRDxvT+s9f1RLoNfGUSeumlA0g0uZknUj+VMJOt79q1qwiNCu8EdzThxcSkqysN3sZhm/yr5l9DGekPTalcAqHzkh1akXV2beBHlMwauQERJiC0TeTQRELcFOCPb2xqa+rIPpO0l+N8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060622100247.GA22462@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <ksrinivasan@xxxxxxxxxx> <44991A88.E57C.0030.0@xxxxxxxxxx> <E1Ft3fM-0002TR-00@xxxxxxxxxxxxxxxxx> <20060621162818.GA19690@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <62b0912f0606211239o67824f6al58905dc2657309be@xxxxxxxxxxxxxx> <20060621212649.GA20843@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <62b0912f0606220257i13487e63xf4667f2630ed764d@xxxxxxxxxxxxxx> <20060622100247.GA22462@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Emmanuel Ackaouy wrote:
Let me know if you have any other questions.
It's useful to discuss design philosophy on the list.

Well, if you don't mind! :-)...

The first sentence was actually a question too:
Migrating 1 VCPU across 2 CPUs, or
swapping all 3 VCPUs around in a ring-fashion?

To explain myself a bit more, I was wondering whether the scheduler
conceptually can be said to work a little like this (VCPUs mapped to
CPUs in a "ring-fashion"):

(VCPUs = A, B, C)

Time     CPU1  CPU2
0ms      A     B
30ms     B     C
60ms     C     A
90ms     A     B
120ms    B     C
...etc...

This would give 30ms slices with a time-to-wait for scheduling of 30ms.

Or perhaps more like this:
Time     CPU1  CPU2
0ms      A     B
30ms     A     C
60ms     B     C
90ms     B     A
120ms    C     A
...etc...

Which gives 60ms slices (warmer cache, yummi) but still with a
time-to-wait for scheduling of 30ms.

The latter obviously being a better algorithm, cache-wise...

Hope it's not stupid questions :-).

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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