From: Jon Loeliger <jdl@netgate.com>
To: Archit Pandey <architpandeynitk@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
dev@dpdk.org, users@dpdk.org,
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: Re: [dpdk-users] [dpdk-dev] Queue Management Support in DPDK
Date: Sun, 2 Aug 2020 11:53:39 -0500 [thread overview]
Message-ID: <CAFTgdxcLEQTrc8eV+HNaoyYeHH2Su9-VGVkT71JGga4XwX3nbg@mail.gmail.com> (raw)
In-Reply-To: <CANtWViMortpg6zFqzCRuhRp1v0UbAxHaqtuCf8E_+gsH-SRe8Q@mail.gmail.com>
On Sun, Aug 2, 2020 at 4:43 AM Archit Pandey <architpandeynitk@gmail.com>
wrote:
> Hi Stephen,
>
> Thanks for the reply.
>
> On Thu, Jul 30, 2020 at 12:37 AM Stephen Hemminger
> <stephen@networkplumber.org> wrote:
> >
> > rte_sched is not a generic AQM mechanism. You will have to write a new
> > replacement for rte_sched if you want something else.
>
> Yes, we did realize that rte_sched is not suitable for AQM algorithms.
> We have implemented a bare-bones AQM mechanism that is independent of
> rte_sched.
> Using this implementation we have successfully added and tested PIE and
> CoDel.
>
> > I would recommend starting with Cake. It is latest and most complete
> > and the developers are active and friendly.
>
> CAKE can be added using what we have built, but before we do that we wanted
> to know if such a feature would be welcomed by the community.
In a word, yes.
> Subsequently, we will submit an RFC patch series to the dev mailing list.
>
> Thanks,
> Archit Pandey.
>
HTH,
jdl
prev parent reply other threads:[~2020-08-02 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 18:37 [dpdk-users] " Archit Pandey
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 [this message]
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=CAFTgdxcLEQTrc8eV+HNaoyYeHH2Su9-VGVkT71JGga4XwX3nbg@mail.gmail.com \
--to=jdl@netgate.com \
--cc=anandtarun2@gmail.com \
--cc=architpandeynitk@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=stephen@networkplumber.org \
--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).