| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] [0/3] DomGrp/SchedGrp Merge RFC
|
To: |
Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> |
|
Subject: |
Re: [Xen-devel] [0/3] DomGrp/SchedGrp Merge RFC |
|
From: |
Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx> |
|
Date: |
Wed, 6 Feb 2008 10:42:12 +0000 |
|
Cc: |
Chris <hap10@xxxxxxxxxxxxxx>, "Mike D. Day" <ncmike@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|
Delivery-date: |
Wed, 06 Feb 2008 02:57:29 -0800 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<C3CF3E71.1C042%Keir.Fraser@xxxxxxxxxxxx> |
|
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> |
|
Mail-followup-to: |
Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, Chris <hap10@xxxxxxxxxxxxxx>, "Mike D. Day" <ncmike@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|
References: |
<20080206102723.GA4338@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C3CF3E71.1C042%Keir.Fraser@xxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Mutt/1.5.12-2006-07-14 |
Keir Fraser, le Wed 06 Feb 2008 10:37:37 +0000, a écrit :
> On 6/2/08 10:27, "Samuel Thibault" <samuel.thibault@xxxxxxxxxxxxx> wrote:
>
> >> I'm driven by concrete use cases. Several of the upcoming uses you mention
> >> need careful consideration of what they are useful for, to determine the
> >> best way to design them into the system. Take resource sharing. Stub
> >> domains
> >> sharing scheduler credits with the HVM guest is a rather special case, and
> >> one where a master/slave relationship is not unreasonable (and hence in
> >> this
> >> case I think it is arguable whether it is actually a good fit with domgrps
> >> after all).
> >
> > Actually, in my former research team in Bordeaux, they would like to
> > write a small domain that computes the scheduling of a bunch of others,
> > for parallel scientific computing.
>
> Well that sounds plausible, but I'm not sure how resource pools or domgrps
> would help with that. It sounds like a delegation mechanism (of privilege
> and/or resource) would be more appropriate.
Sure, delegation will be needed, but there needs to be a way to specify
which domains that scheduler has control on.
Samuel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home