|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] [PATCH] scheduler rate controller
To: |
George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, "Lv, Hui" <hui.lv@xxxxxxxxx> |
Subject: |
Re: [Xen-devel] [PATCH] scheduler rate controller |
From: |
Keir Fraser <keir@xxxxxxx> |
Date: |
Mon, 24 Oct 2011 17:57:27 +0100 |
Cc: |
"Duan, Jiangang" <jiangang.duan@xxxxxxxxx>, "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Dong, Eddie" <eddie.dong@xxxxxxxxx> |
Delivery-date: |
Mon, 24 Oct 2011 09:59:31 -0700 |
Dkim-signature: |
v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=DOEB6O4cqwvF1yxHZ//nOsy5bw25BBmq9VH6QZVIOC4=; b=S48V1LaOTFjG9wJHOAA/8HMJcrpMSEhPSScOtiY+doKJU8g1srfLKj+p4ES2N0tsHP zXxKnNT569VuEt2Md6nkqWLKoHvmRfcgSEsXg1JfSC59Wv32r2g1DUVrt0KQcwLJ075b tvfj7J8WubZLlsf/I+8hqd4k7i5RUP5Q4/jDg= |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<CAFLBxZZ9nqeb7CVqTZCsEtJRjgGMTHF2Ak929kvauj2KUFSOyg@xxxxxxxxxxxxxx> |
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> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Thread-index: |
AcySbgJTwF9STDS7aEez2D8SH4kEvA== |
Thread-topic: |
[Xen-devel] [PATCH] scheduler rate controller |
User-agent: |
Microsoft-Entourage/12.30.0.110427 |
On 24/10/2011 17:17, "George Dunlap" <George.Dunlap@xxxxxxxxxxxxx> wrote:
> * I'm not sure I like the idea of doing this at the generic level than
> at the specific scheduler level -- e.g., inside of credit1. For
> better or for worse, all aspects of scheduling work together, and even
> small changes tend to have a significant effect on the emergent
> behavior. I understand why you'd want this in the generic scheduling
> code; but it seems like it would be better for each scheduler to
> implement a rate control independently.
Yes, this doesn't belong in schedule.c.
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|