xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Zhigang Wang <zhigang.x.wang@oracle.com>
To: Kuriakose Mathew <kmathew123@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: bandwidth limit and guarantee for DomUs
Date: Mon, 24 May 2010 08:02:10 +0800	[thread overview]
Message-ID: <4BF9C202.2010000@oracle.com> (raw)
In-Reply-To: <AANLkTime6Jlq5Myb2wZk3dZVNosadFSII8hNcAEDkTZK@mail.gmail.com>

You reimplemented this:
http://xenbits.xensource.com/xen-unstable.hg?rev/dadadf9aeee7 ? This patch is
for outbound (from domU) traffic only.

For inbound (from domU), you can use tc on vifx.y.

Zhigang

On 05/22/2010 02:38 PM, Kuriakose Mathew wrote:
> 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
> <mailto: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
> 
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

      reply	other threads:[~2010-05-24  0:02 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
2010-05-24  0:02   ` Zhigang Wang [this message]

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=4BF9C202.2010000@oracle.com \
    --to=zhigang.x.wang@oracle.com \
    --cc=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).