From: Joshua Ani <jani@paloaltonetworks.com>
To: dev@dpdk.org
Subject: Port traffic shaping
Date: Thu, 7 Jul 2022 14:43:26 -0400 [thread overview]
Message-ID: <CAMR_VoWs4PLfYfZz5ptB_tyZLd8pOJtFBTnUDY-eGZzdVjT6wg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
I noticed that traffic shaping is implemented for the subport and pipe
level, but not the port level. Why is this? When I tried implementing it,
most of the work was just copying subport traffic shaping logic for the
port, though I had to make some changes to fix a bandwidth issue with
multiple ports being processed on the same core. Could this be the reason,
or is it something else?
[-- Attachment #2: Type: text/html, Size: 414 bytes --]
reply other threads:[~2022-07-07 18:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAMR_VoWs4PLfYfZz5ptB_tyZLd8pOJtFBTnUDY-eGZzdVjT6wg@mail.gmail.com \
--to=jani@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).