DPDK patches and discussions
 help / color / mirror / Atom feed
From: Venky Venkatesh <vvenkatesh@paloaltonetworks.com>
To: dev@dpdk.org
Subject: [2nd Try]:Re: Traffic Management API Questions
Date: Tue, 10 Jan 2023 00:52:17 -0800	[thread overview]
Message-ID: <CAJ4WCt+XwKutUmzwAGBSb__o391BNN98rhO7bjTKgjY6CXwuHg@mail.gmail.com> (raw)
In-Reply-To: <CAJ4WCt+4mW488EAH_h3F3dhe-06KnydGg54A=hb=P_yTzt+NeA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1946 bytes --]

Hi,
Can someone pls get back on these
Thanks
-Venky

On Thu, Jan 5, 2023 at 4:07 AM Venky Venkatesh <
vvenkatesh@paloaltonetworks.com> wrote:

> Hi,
> I was looking at the DPDK Traffic Management API. I wanted to clarify some
> things that I understand from the code (for software based TM
> implementation (at 20.11)) vs the documentation.
>
>    - The documentation says "Traffic shaping: single/*dual rate,* private
>    (*per node*) and shared (by *multiple nodes*) shapers" are supported.
>    However it appears that the code supports only *single *rate shapers.
>    Is my understanding correct?
>       - If not, pls point me to where dual rate shaping is supported in
>       the software based TM implementation code.
>       - However, if my understanding is correct, can the authors clarify
>       the nature of issues they ran into in supporting dual rate (which thus
>       prevented them from implementing it)?
>    - The documentation comment above sounds like every node can have
>    shapers. However it appears that the code does not support shaping at the
>    port level. Again the same questions as above(regarding the accuracy of my
>    understanding and if it is accurate, the reasons from the author for not
>    supporting it)
>    - At the level of the TM API (*and* the associated software TM
>    implementation) are there any restrictions on the number of levels of QoS
>    hierarchy we can construct?
>    - Lastly, does the QoS framework API (which I suppose is built on
>    lower level building blocks including the TM API) expose the entire
>    capabilities of the TM API (e.g. dual rate shapers, shapers at port level,
>    > 4 levels of shaping etc.)? From the reading of the documentation it
>    appears that there may be restrictions imposed by the QoS framework API on
>    top of what TM API imposes. Can someone pls confirm this (and if so, the
>    reason for doing so)?
>
>
> Thanks
> -Venky
>
>

[-- Attachment #2: Type: text/html, Size: 2649 bytes --]

  reply	other threads:[~2023-01-10  8:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 12:07 Venky Venkatesh
2023-01-10  8:52 ` Venky Venkatesh [this message]
2023-01-10 10:54   ` [2nd Try]:Re: " Singh, Jasvinder
2023-01-11 11:55     ` Venky Venkatesh
2023-01-11 17:24       ` Singh, Jasvinder
2023-01-16  8:05         ` Venky Venkatesh
2023-01-16 11:38           ` Singh, Jasvinder
2023-01-16 13:59             ` Venky Venkatesh

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=CAJ4WCt+XwKutUmzwAGBSb__o391BNN98rhO7bjTKgjY6CXwuHg@mail.gmail.com \
    --to=vvenkatesh@paloaltonetworks.com \
    --cc=dev@dpdk.org \
    /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).