[dpdk-dev] DPDK QoS scheduler changes, are we there yet?

[dpdk-dev] DPDK QoS scheduler changes, are we there yet?

[Gladchun, Glenn]

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?

Thanks,

Glenn G

This electronic message and any files transmitted with it contains information from iDirect, which may be privileged, proprietary and/or confidential. It is intended solely for the use of the individual or entity to whom they are addressed. 
If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of 
this email is strictly prohibited. If you received this email in error, please delete it and immediately notify the sender.

Re: [dpdk-dev] DPDK QoS scheduler changes, are we there yet?

[Ferruh Yigit]

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.

> 
> Thanks,
> 
> Glenn G
> 
> This electronic message and any files transmitted with it contains information from iDirect, which may be privileged, proprietary and/or confidential. It is intended solely for the use of the individual or entity to whom they are addressed. 
> If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of 
> this email is strictly prohibited. If you received this email in error, please delete it and immediately notify the sender.
> 

Re: [dpdk-dev] DPDK QoS scheduler changes, are we there yet?

[Singh, Jasvinder]

> -----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
  

Re: [dpdk-dev] DPDK QoS scheduler changes, are we there yet?

[Gladchun, Glenn]

Jasvinder,

Thanks! Got confused by outdated documentation that still references old design...

Glenn

Sent from iPad
________________________________
From: Singh, Jasvinder <jasvinder.singh@intel.com>
Sent: Thursday, October 31, 2019 1:45 PM
To: Gladchun, Glenn; dev@dpdk.org
Cc: Dumitrescu, Cristian; Yigit, Ferruh
Subject: RE: [dpdk-dev] DPDK QoS scheduler changes, are we there yet?

***WARNING! THIS EMAIL ORIGINATES FROM OUTSIDE ST ENGINEERING IDIRECT.***

> -----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<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

This electronic message and any files transmitted with it contains information from iDirect, which may be privileged, proprietary and/or confidential. It is intended solely for the use of the individual or entity to whom they are addressed. 
If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of 
this email is strictly prohibited. If you received this email in error, please delete it and immediately notify the sender.

Re: [dpdk-dev] DPDK QoS scheduler changes, are we there yet?

[David Marchand]

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.


Thanks.


--
David Marchand

Re: [dpdk-dev] DPDK QoS scheduler changes, are we there yet?

[Singh, Jasvinder]

> -----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.

[dpdk-dev] DPDK QoS scheduler changes, are we there yet?

[Gladchun, Glenn]

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?

Thanks,

Glenn G

This electronic message and any files transmitted with it contains information from iDirect, which may be privileged, proprietary and/or confidential. It is intended solely for the use of the individual or entity to whom they are addressed. 
If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of 
this email is strictly prohibited. If you received this email in error, please delete it and immediately notify the sender.