Re: [lng-odp] [RFC] api: classification: Create PMR handle on its application

2015-04-14 Thread Ola Liljedahl
Moving a function from one header file to another doesn't really change anything. The classification API isn't optional (but the level of actual functionality is implementation/platform specific). Most users will just include odp.h anyway. I don't disagree with odp_pktio_default_cos_set() having

Re: [lng-odp] [RFC] api: classification: Create PMR handle on its application

2015-04-14 Thread Mike Holmes
On 14 April 2015 at 04:53, Ola Liljedahl ola.liljed...@linaro.org wrote: Moving a function from one header file to another doesn't really change anything. The classification API isn't optional (but the level of actual functionality is implementation/platform specific). Most users will just

Re: [lng-odp] [RFC] api: classification: Create PMR handle on its application

2015-04-09 Thread Bala Manoharan
On 9 April 2015 at 14:38, Taras Kondratiuk taras.kondrat...@linaro.org wrote: + mailing list that I've missed initially in the RFC. On 04/08/2015 10:25 PM, Rosenboim, Leonid wrote: Taras, I actually agree with you that a change in the API is justified that combines the in and out CoS

Re: [lng-odp] [RFC] api: classification: Create PMR handle on its application

2015-04-09 Thread Taras Kondratiuk
+ mailing list that I've missed initially in the RFC. On 04/08/2015 10:25 PM, Rosenboim, Leonid wrote: Taras, I actually agree with you that a change in the API is justified that combines the in and out CoS values are provided at the time of PMR creation, instead of using a separate function.