IIRC, the cap functionality is useful primarily for application
licensing, e.g. to ensure that an app licensed for 2 cpus
never gets more than 2 cpus, even if all other cpus are idle.
I suppose it could also be used by a webhosting provider to
create similar limits to allow selling of an added-value tier
(e.g. "uncapped", kind of a poor man's cloud computing).
Given that, I'd say this is a much too restricted forum
(primarily developers) to ask and, even if it's not being
used today, pulling it out seems premature unless there's
a *really* good reason.
My two cents,
Dan
> -----Original Message-----
> From: George Dunlap [mailto:George.Dunlap@xxxxxxxxxxxxx]
> Sent: Tuesday, January 20, 2009 12:09 PM
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-devel] Is anyone using the credit scheduler "cap"
> functionality?
>
>
> I'm in the process of revising the credit scheduler design, and I'd
> like to know how important it is to maintain the "cap" functionality
> of the credit scheduler. If you use it, or know of someone who does,
> could you let me know?
>
> If you don't know what it is, you probably aren't using it. :-)
>
> Peace,
> -George
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|