From: "Singh, Jasvinder" <jasvinder.singh@intel.com>
To: "Gladchun, Glenn" <ggladchun@idirect.net>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] DPDK QoS scheduler changes, are we there yet?
Date: Thu, 31 Oct 2019 17:45:06 +0000 [thread overview]
Message-ID: <54CBAA185211B4429112C315DA58FF6D3FE5D002@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <25abaaf3-9a92-a3a5-c2a1-3015ef809546@intel.com>
> -----Original Message-----
> From: Yigit, Ferruh <ferruh.yigit@intel.com>
> Sent: Thursday, October 31, 2019 3:14 PM
> To: Gladchun, Glenn <ggladchun@idirect.net>; dev@dpdk.org
> Cc: Singh, Jasvinder <jasvinder.singh@intel.com>; Dumitrescu, Cristian
> <cristian.dumitrescu@intel.com>
> Subject: Re: [dpdk-dev] DPDK QoS scheduler changes, are we there yet?
>
> On 10/30/2019 6:35 PM, Gladchun, Glenn wrote:
> > Hi guys,
> >
> > 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?
>
> cc'ed Jasvinder & Cristian.
>
> >
Hi Glenn,
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.
Thanks,
Jasvinder
next prev parent reply other threads:[~2019-10-31 17:45 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 [this message]
2019-11-01 19:32 ` Gladchun, Glenn
2019-11-04 7:48 ` David Marchand
2019-11-04 10:09 ` Singh, Jasvinder
-- 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=54CBAA185211B4429112C315DA58FF6D3FE5D002@IRSMSX103.ger.corp.intel.com \
--to=jasvinder.singh@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ggladchun@idirect.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).