Re: [dpdk-dev] [RFC v2] sched: parameterize QoS traffic-classes and queues

2018-02-16 Thread Stephen Hemminger
On Fri, 16 Feb 2018 15:44:13 + alangordonde...@gmail.com wrote: > - qindex = tc_index * 4; > - > - pipe->wrr_tokens[qindex] = (grinder->wrr_tokens[0] & > grinder->wrr_mask[0]) > - >> RTE_SCHED_WRR_SHIFT; > - pipe->wrr_tokens[qindex + 1] = (grinder->wrr_tokens[1] & >

Re: [dpdk-dev] [RFC v2] sched: parameterize QoS traffic-classes and queues

2018-02-16 Thread Stephen Hemminger
On Fri, 16 Feb 2018 15:44:13 + alangordonde...@gmail.com wrote: > > +static inline uint32_t > +rte_min_pos_n_u16(uint16_t *x, uint32_t n) The table (x) is const > +{ > + uint32_t index; > + uint32_t min_index = 0; > + uint16_t min_value = UINT16_MAX; > + > + for (index = 0;

[dpdk-dev] [RFC v2] sched: parameterize QoS traffic-classes and queues

2018-02-16 Thread alangordondewar
From: Alan Dewar The DPDK QoS framework has hierarchy of QoS scheduling elements: port, subport, pipe, traffic-class and queue. The first two levels of the hierarchy are flexible (port and subport) in the number child nodes that each parent can have, but from the pipe layer down the number of ch