From: Stephen Hemminger <firstname.lastname@example.org> To: Archit Pandey <email@example.com> Cc: firstname.lastname@example.org, email@example.com, Gokul Bargaje <firstname.lastname@example.org>, "Mohit P. Tahiliani" <email@example.com>, Tarun Anand <firstname.lastname@example.org>, Sanjana Krishnam <email@example.com>, "Avinash ." <firstname.lastname@example.org>, Leslie Monis <email@example.com> Subject: Re: [dpdk-dev] Queue Management Support in DPDK Date: Wed, 29 Jul 2020 12:07:14 -0700 Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <CANtWViMLg3ArDhdj8q+VYst1_UHErD1K9CudNBoMTc+4V+Gv8g@mail.gmail.com> On Thu, 30 Jul 2020 00:07:29 +0530 Archit Pandey <email@example.com> wrote: > 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. rte_sched is not a generic AQM mechanism. You will have to write a new replacement for rte_sched if you want something else. I would recommend starting with Cake. It is latest and most complete and the developers are active and friendly.
next prev parent reply index Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-29 18:37 Archit Pandey 2020-07-29 19:07 ` Stephen Hemminger [this message] 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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
DPDK-dev Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/dpdk-dev/0 dpdk-dev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 dpdk-dev dpdk-dev/ https://lore.kernel.org/dpdk-dev \ email@example.com public-inbox-index dpdk-dev Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.dpdk.dev AGPL code for this site: git clone https://public-inbox.org/public-inbox.git