From: "Singh, Jasvinder" <jasvinder.singh@intel.com>
To: David Marchand <david.marchand@redhat.com>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: "Gladchun, Glenn" <ggladchun@idirect.net>,
"dev@dpdk.org" <dev@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] DPDK QoS scheduler changes, are we there yet?
Date: Mon, 4 Nov 2019 10:09:56 +0000 [thread overview]
Message-ID: <54CBAA185211B4429112C315DA58FF6D3FE5F6AE@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <CAJFAV8y+2bT8bpLXxinCBxSW7QX2d6G6uW3MatNkhM2ScpAVww@mail.gmail.com>
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Monday, November 4, 2019 7:48 AM
> To: Singh, Jasvinder <jasvinder.singh@intel.com>; Dumitrescu, Cristian
> <cristian.dumitrescu@intel.com>
> Cc: Gladchun, Glenn <ggladchun@idirect.net>; dev@dpdk.org; Yigit, Ferruh
> <ferruh.yigit@intel.com>; Thomas Monjalon <thomas@monjalon.net>
> Subject: Re: [dpdk-dev] DPDK QoS scheduler changes, are we there yet?
>
> On Thu, Oct 31, 2019 at 6:45 PM Singh, Jasvinder
> <jasvinder.singh@intel.com> wrote:
> > > On 10/30/2019 6:35 PM, Gladchun, Glenn wrote:
> > > > I stumbled upon this 11 month old post
> > > > (https://narkive.com/ZwBXg4Xe)
> > > that goes over future enhancements to the scheduler. All of them
> > > are vital, and I am especially interested in 16 TCs per pipe…
> > > Christian and/or Jasvinder, is the future here yet in some tangible shape
> or form?
> > >
> > The DPDK sched library has been modified to increase the number of traffic
> classes per pipe, please refer source code available on dpdk master to see
> the changes.
>
> We need the fixes for the documentation.
> These should have been part of the modifications.
>
>
I have already sent patches on documentation updates.
next prev parent reply other threads:[~2019-11-04 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 18:35 Gladchun, Glenn
2019-10-31 15:13 ` Ferruh Yigit
2019-10-31 17:45 ` Singh, Jasvinder
2019-11-01 19:32 ` Gladchun, Glenn
2019-11-04 7:48 ` David Marchand
2019-11-04 10:09 ` Singh, Jasvinder [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-30 15:32 Gladchun, Glenn
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=54CBAA185211B4429112C315DA58FF6D3FE5F6AE@IRSMSX103.ger.corp.intel.com \
--to=jasvinder.singh@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ggladchun@idirect.net \
--cc=thomas@monjalon.net \
/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).