> -----Original Message----- > From: Stephen Hemminger [mailto:step...@networkplumber.org] > Sent: Friday, August 18, 2017 6:22 PM > To: Dumitrescu, Cristian <cristian.dumitre...@intel.com> > Cc: Kevin Yan <kevin....@mavenir.com>; dev@dpdk.org > Subject: Re: [dpdk-dev] DPDK qos support for 40G port > > On Fri, 18 Aug 2017 11:24:12 +0000 > "Dumitrescu, Cristian" <cristian.dumitre...@intel.com> wrote: > > > Hi Kevin, > > > > > Hi Cristian, > > > Sorry to bother again, could you give suggestions/hints of code change to > > > support single 40G port? Because in our setup, we will use single 40G > port > > > (Intel XL710) as the network interface. > > > > > > Or is there any workaround to bypass the limitation?(we are not willing to > > > use 4*10G setup) > > > > > > Thanks. > > > > > > > Probably the easiest thing to do as workaround to support single port of > 40GbE rate is to change the code so that each credit is equivalent to 2 bytes > instead of one. This is likely to result in some scheduling accuracy loss, > but it > can be implemented relatively quickly while avoiding complex code changes. > > > > Regards, > > Cristian > > > > Maybe it is time to deprecate existing QoS since it has so many fixed limits > and start a new version which supports up to 400G and many more classes. > > Something that integrated better with your new QoS framework.
s/deprecate/improve I am working to push some updates to librte_meter library, librte_sched to follow.
