[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Re: bandwidth limit and guarantee for DomUs

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Kuriakose Mathew <kmathew123@xxxxxxxxx>
  • Date: Sat, 22 May 2010 12:08:54 +0530
  • Delivery-date: Fri, 21 May 2010 23:40:15 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=MnmyyDn4rorw+plR3sTeUbSL5vA2NSoPFUY7IZTkLHg3FHXAB2XnLEKz3SE/LCn9kz aO8uwPSETZgpETx57l1pNmiBsxc8QVxhle1jRjlJvtdDjDscmwXQhOWP/9ZyfLH0j2QL 5hz9KnxT4VCr2tamwmyZJ8cAWmgvK5/Zf7rMU=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Will the CPU scheduler algo for providing weights work in case of bandwidth weights?
Or any other better suggestions in this direction.

Thanks in advance

On Fri, May 21, 2010 at 8:04 PM, Kuriakose Mathew <kmathew123@xxxxxxxxx> wrote:

I have done a small code modification so that the bandwidth limit of each domU can be limited.

The implementation goes like this

In the file  linux-2.6-xen-sparse/drivers/xen/netback/netback.c
In the function, net_tx_action
netif->remaining_credit and  netif->credit_usec values are assigned such that in credit_usec seconds the domain can send remaining_credit bytes.

Now I want to implement something like providing guarantees to domains. That is whatever be the bandwidth utilization of say DomU2 DomU1 should be able to deliver at minimum rate similar to setting cpu cap and weights.

Can someone point me to some algorithm or reference in this direction

Thanks in advance

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.