> -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monja...@6wind.com] > Sent: Tuesday, December 6, 2016 10:14 PM > To: Stephen Hemminger <step...@networkplumber.org> > Cc: dev@dpdk.org; Dumitrescu, Cristian <cristian.dumitre...@intel.com> > Subject: Re: [dpdk-dev] [RFC] ethdev: abstraction layer for QoS hierarchical > scheduler > > 2016-12-06 11:51, Stephen Hemminger: > > Rather than reinventing wheel which seems to be DPDK Standard > > Procedure, could an existing abstraction be used? > > Stephen, you know that the DPDK standard procedure is to consider > reviews and good comments ;)
Thomas, sorry for not CC-ing you (as the librte_ether maintainer) when the initial RFC was sent out, comments from you would be welcomed and much appreciated as well! Also same kind reminder for other people in the community as well. (CC-ing just a few). Some of you have expressed interest in the past for building an abstraction layer for QoS hierarchical scheduler, so here is the RFC for it which we can evolve together. Let's make sure we build a robust layer that fits well for all devices and vendors that are part of the DPDK community!
