DPDK patches and discussions
 help / color / mirror / Atom feed
From: Sangjin Han <sangjin@eecs.berkeley.edu>
To: Greg Smith <gregsmith@juniper.net>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] QoS Question
Date: Tue, 21 Apr 2015 04:58:18 +0000	[thread overview]
Message-ID: <CAPG33HRC9g_AoHcMRyETrtip0rykkwf7XhpgBZOMEytzob_0Pg@mail.gmail.com> (raw)
In-Reply-To: <BN1PR05MB280069BC605566E6014E7CBA8E00@BN1PR05MB280.namprd05.prod.outlook.com>

Hi,

According to "21.2.4.6.6.2", it seems that the implementation is supposed
to achieve max-min fairness. In your example, the effective cap of single
active pipe should be 1Mbps, given the total demand of other 1999 pipes is
less than 999Mbps.

Sangjin

On Mon, Apr 20, 2015 at 9:40 AM Greg Smith <gregsmith@juniper.net> wrote:

> Hi DPDK team,
>
> The docs on QoS (http://dpdk.org/doc/guides/prog_guide/qos_framework.html#
> ) describe the traffic class (TC) as follows:
> 1 - The  TCs of the same pipe handled in strict priority order.
> 2 - Upper limit enforced per TC at the pipe level.
> 3 - Lower priority TCs able to reuse pipe bandwidth currently unused by
> higher priority TCs.
> 4 - When subport TC is oversubscribed (configuration time event), pipe TC
> upper limit is capped to a dynamically adjusted value that is shared by all
> the subport pipes.
>
> Can someone describe how and when the TC upper limit is "dynamically"
> changed?
>
> For example, assume there's a 1Gb/s port and a single 1Gb/s subport and
> 2000 pipes each of 1Mb/s (total pipes = 2Gb/s which is > the 1Gb/s subport
> which I think means "oversubscribed" as used in the doc). Each Pipe has a
> single TC.
> In that case, would each pipe be shaped to an upper limit of 0.5 Mb/s?
> What if there was no traffic on 1999 pipes, would the single active pipe
> still be limited to 0.5 Mb/s?
> What if the number of pipes changes without restarting the OS, how does
> that change the behavior?
>
> BTW, great docs overall, thanks for writing those up.
>
> Thanks,
>
> Greg Smith
>
>
>
>

  reply	other threads:[~2015-04-21  4:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 16:39 Greg Smith
2015-04-21  4:58 ` Sangjin Han [this message]
2015-04-24 11:19 ` Dumitrescu, Cristian

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=CAPG33HRC9g_AoHcMRyETrtip0rykkwf7XhpgBZOMEytzob_0Pg@mail.gmail.com \
    --to=sangjin@eecs.berkeley.edu \
    --cc=dev@dpdk.org \
    --cc=gregsmith@juniper.net \
    /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).