From: Kuriakose Mathew <kmathew123@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Re: bandwidth limit and guarantee for DomUs
Date: Sat, 22 May 2010 12:08:54 +0530 [thread overview]
Message-ID: <AANLkTime6Jlq5Myb2wZk3dZVNosadFSII8hNcAEDkTZK@mail.gmail.com> (raw)
In-Reply-To: <AANLkTilTZ016iGhYr594-TlCNxrJWlXZs7YfXrawfcOY@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 973 bytes --]
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
Mathew
On Fri, May 21, 2010 at 8:04 PM, Kuriakose Mathew <kmathew123@gmail.com>wrote:
> Hi,
>
> 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
> Mathew
>
[-- Attachment #1.2: Type: text/html, Size: 1307 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-05-22 6:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 14:34 bandwidth limit and guarantee for DomUs Kuriakose Mathew
2010-05-22 6:38 ` Kuriakose Mathew [this message]
2010-05-24 0:02 ` Zhigang Wang
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=AANLkTime6Jlq5Myb2wZk3dZVNosadFSII8hNcAEDkTZK@mail.gmail.com \
--to=kmathew123@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).