From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Chris <hap10@tycho.ncsc.mil>, "Mike D. Day" <ncmike@us.ibm.com>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [0/3] DomGrp/SchedGrp Merge RFC
Date: Wed, 6 Feb 2008 10:42:12 +0000 [thread overview]
Message-ID: <20080206104212.GB4338@implementation.uk.xensource.com> (raw)
In-Reply-To: <C3CF3E71.1C042%Keir.Fraser@cl.cam.ac.uk>
Keir Fraser, le Wed 06 Feb 2008 10:37:37 +0000, a écrit :
> On 6/2/08 10:27, "Samuel Thibault" <samuel.thibault@eu.citrix.com> 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
next prev parent reply other threads:[~2008-02-06 10:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 16:02 [RFC 1/2] Domain Groups - VMM Support Chris
2007-12-18 16:13 ` Samuel Thibault
2007-12-19 15:19 ` Chris
2008-01-22 14:20 ` [RESEND] " Chris
2008-01-22 14:40 ` Samuel Thibault
2008-01-22 14:51 ` Chris
[not found] ` <20080122144325.GP4365@implementation.uk.xensource.com>
2008-01-22 18:22 ` grub-like modules Chris
2008-01-31 20:04 ` Domain Groups - VMM Support Mike D. Day
2008-02-01 20:33 ` Chris
2008-02-04 19:14 ` [0/3] DomGrp/SchedGrp Merge RFC Chris
2008-02-04 22:56 ` Keir Fraser
2008-02-05 22:20 ` Chris
2008-02-06 9:20 ` Keir Fraser
2008-02-06 10:27 ` Samuel Thibault
2008-02-06 10:37 ` Keir Fraser
2008-02-06 10:42 ` Samuel Thibault [this message]
2008-02-06 11:00 ` Keir Fraser
2008-02-06 15:22 ` Chris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080206104212.GB4338@implementation.uk.xensource.com \
--to=samuel.thibault@eu.citrix.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=hap10@tycho.ncsc.mil \
--cc=ncmike@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.