[dpdk-dev] 17.02 Roadmap

[Pattan, Reshma]

Hi Thomas,


> -----Original Message-----
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Monday, October 10, 2016 9:43 PM
> To: O'Driscoll, Tim <tim.odriscoll at intel.com>
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] 17.02 Roadmap
> 
> Thanks Tim for the interesting inputs.
> Some of them may require a dedicated thread to continue the discussion based
> on some preliminary specifications or drafts.
> 
> 2016-10-10 16:13, O'Driscoll, Tim:
> > Elastic Flow Distributor: The Elastic Flow Distributor (EFD) is a flow-based load
> balancing library which scales linearly for both lookup and insert with the
> number of threads or cores.  EFD lookup uses a "perfect hashing" scheme where
> only the information needed to compute a key's value (and not the key itself) is
> stored in the lookup table, thus reducing CPU cache storage requirements.
> 
> What is the scope of this library? Just apply rte_hash to a flow table?
> Or is it also sending the packets in some queues?
> Does it depend of librte_distributor?
> 
> > Extended Stats (Latency and Bit Rate Statistics): Enhance the Extended NIC
> Stats (Xstats) implementation to support the collection and reporting of latency
> and bit rate measurements. Latency statistics will include min, max and average
> latency, and jitter. Bit rate statistics will include peak and average bit rate
> aggregated over a user-defined time period. This will be implemented for IXGBE
> and I40E.
> 
> Are they retrieved from hardware or just computed in software?

Computed in software. 

> Could we have some drivers hook to compute them in a generic layer?
Since more stats are coming into DPDK , we planned to avoid adding new code into ethdev library. So adding couple of new libraries to deal with future stats.
1)There will be a new stats library which will provide APIs like, stats registration,  stats update and get stats .

2) Another latency stats, bitrate library. This new library uses rte_eth rx/tx callbacks  to mark  Rx timestamp in Rx callback and calculate latency in Tx callback.

The new stats library(1)  shall be used by latency stats , bit rate stats (2) and further new stats to register themselves and push their values to stats library. 
Stats library get APIs will be called by existing xstats get API of the ethdev library  to display all new stats as part of xstats.

Thanks,
Reshma