On Sun, Jun 07, 2009 at 09:04:49AM +0300, Avi Kivity wrote: > Bharata B Rao wrote: >> On Fri, Jun 05, 2009 at 09:01:50AM +0300, Avi Kivity wrote: >> >>> Bharata B Rao wrote: >>> >>>> But could there be client models where you are required to strictly >>>> adhere to the limit within the bandwidth and not provide more (by advancing >>>> the bandwidth period) in the presence of idle cycles ? >>>> >>> That's the limit part. I'd like to be able to specify limits and >>> guarantees on the same host and for the same groups; I don't think >>> that works when you advance the bandwidth period. >>> >>> I think we need to treat guarantees as first-class goals, not >>> something derived from limits (in fact I think guarantees are more >>> useful as they can be used to provide SLAs). >>> >> >> I agree that guarantees are important, but I am not sure about >> >> 1. specifying both limits and guarantees for groups and >> > > Why would you allow specifying a lower bound for cpu usage (a > guarantee), and upper bound (a limit), but not both? I was saying that we specify only limits and not guarantees since it can be worked out from limits. Initial thinking was that the kernel will be made aware of only limits and users could set the limits appropriately to obtain the desired guarantees. I understand your concerns/objections on this and we will address this in our next version of RFC as Balbir said. Regards, Bharata. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
