From: Archit Pandey <architpandeynitk@gmail.com>
To: dev@dpdk.org, users@dpdk.org
Cc: Gokul Bargaje <gokulbargaje.182009@nitk.edu.in>,
"Mohit P. Tahiliani" <tahiliani@nitk.edu.in>,
Tarun Anand <anandtarun2@gmail.com>,
Sanjana Krishnam <sanjanakrishnam@gmail.com>,
"Avinash ." <avinash.182cs009@nitk.edu.in>,
Leslie Monis <lesliemonis@gmail.com>
Subject: [dpdk-users] Queue Management Support in DPDK
Date: Thu, 30 Jul 2020 00:07:29 +0530 [thread overview]
Message-ID: <CANtWViMLg3ArDhdj8q+VYst1_UHErD1K9CudNBoMTc+4V+Gv8g@mail.gmail.com> (raw)
Hello everyone,
We have been using DPDK's QoS framework over the last year and found
that rte_sched and the provided qos_sched app work great for QoS.
However, when we ventured into trying to add CoDel (to replace RED) as
a dropper to the framework, we faced several challenges due to how
tightly rte_sched and rte_red were coupled together. As we had no
success with rte_sched, we would like to propose a new framework for
queue management in DPDK.
Goals we have in mind for the framework:
- Act as an abstraction for queue management algorithms (AQMs) such as
CoDel, PiE and RED.
- Make it easy for new algorithms to be added.
We’d appreciate feedback on whether such a framework would be welcomed
in the community, or what else could be done for adding queue
management support.
Sincerely,
Archit Pandey.
next reply other threads:[~2020-07-29 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 18:37 Archit Pandey [this message]
2020-07-29 19:07 ` [dpdk-users] [dpdk-dev] " Stephen Hemminger
2020-08-02 9:42 ` Archit Pandey
2020-08-02 16:53 ` Jon Loeliger
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=CANtWViMLg3ArDhdj8q+VYst1_UHErD1K9CudNBoMTc+4V+Gv8g@mail.gmail.com \
--to=architpandeynitk@gmail.com \
--cc=anandtarun2@gmail.com \
--cc=avinash.182cs009@nitk.edu.in \
--cc=dev@dpdk.org \
--cc=gokulbargaje.182009@nitk.edu.in \
--cc=lesliemonis@gmail.com \
--cc=sanjanakrishnam@gmail.com \
--cc=tahiliani@nitk.edu.in \
--cc=users@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).