[dpdk-dev] [RFC v2] Generic flow director/filtering/classification API

2016-11-09 Thread Adrien Mazarguil
Hi Helin and PMD maintainers, On Tue, Nov 08, 2016 at 01:31:05AM +, Zhang, Helin wrote: > Hi Adrien > > Any update on the v1 APIs? We are struggling on that, as we need that for our > development. > May I bring another idea to remove the blocking? > Can we send out the APIs with PMD changes

[dpdk-dev] [RFC v2] Generic flow director/filtering/classification API

2016-11-08 Thread Zhang, Helin
arguil [mailto:adrien.mazarguil at 6wind.com] > Sent: Wednesday, November 2, 2016 7:13 PM > To: Zhang, Helin > Cc: dev at dpdk.org; Thomas Monjalon; Lu, Wenzhuo > Subject: Re: [dpdk-dev] [RFC v2] Generic flow > director/filtering/classification > API > > Hi Helin, > > On Mon, Oct

[dpdk-dev] [RFC v2] Generic flow director/filtering/classification API

2016-11-02 Thread Adrien Mazarguil
t longer! > > -Original Message- > > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Adrien Mazarguil > > Sent: Friday, September 30, 2016 1:11 AM > > To: dev at dpdk.org > > Cc: Thomas Monjalon > > Subject: Re: [dpdk-dev] [RFC v2] Generic flow > >

[dpdk-dev] [RFC v2] Generic flow director/filtering/classification API

2016-10-31 Thread Zhang, Helin
m: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Adrien Mazarguil > Sent: Friday, September 30, 2016 1:11 AM > To: dev at dpdk.org > Cc: Thomas Monjalon > Subject: Re: [dpdk-dev] [RFC v2] Generic flow > director/filtering/classification > API > > On Fri, Aug 19, 2016 at 08:5

[dpdk-dev] [RFC v2] Generic flow director/filtering/classification API

2016-10-12 Thread Zhao1, Wei
Hi Adrien Mazarguil, > -Original Message- > From: Adrien Mazarguil [mailto:adrien.mazarguil at 6wind.com] > Sent: Tuesday, October 11, 2016 4:21 PM > To: Zhao1, Wei > Cc: dev at dpdk.org > Subject: Re: [dpdk-dev] [RFC v2] Generic flow > director/filtering/classif

[dpdk-dev] [RFC v2] Generic flow director/filtering/classification API

2016-10-11 Thread Adrien Mazarguil
Hi Wei, On Tue, Oct 11, 2016 at 01:47:53AM +, Zhao1, Wei wrote: > Hi Adrien Mazarguil, > There is a struct rte_flow_action_rss in rte_flow.txt, the member > rss_conf is a pointer type, is there any convenience in using pointer? > Why not using struct rte_eth_rss_conf rss_conf type,

[dpdk-dev] [RFC v2] Generic flow director/filtering/classification API

2016-10-11 Thread Zhao1, Wei
drien.mazarguil at 6wind.com] > Sent: Monday, October 10, 2016 9:19 PM > To: Zhao1, Wei > Cc: dev at dpdk.org > Subject: Re: [dpdk-dev] [RFC v2] Generic flow > director/filtering/classification > API > > Hi Wei, > > On Mon, Oct 10, 2016 at 09:42:53AM +, Zhao1, Wei wrote

[dpdk-dev] [RFC v2] Generic flow director/filtering/classification API

2016-10-10 Thread Adrien Mazarguil
Hi Wei, On Mon, Oct 10, 2016 at 09:42:53AM +, Zhao1, Wei wrote: > Hi Adrien Mazarguil, > > In your v2 version of rte_flow.txt , there is an action type > RTE_FLOW_ACTION_TYPE_MARK, but there is no definition of struct > rte_flow_action_mark. > And there is an definition of struct

[dpdk-dev] [RFC v2] Generic flow director/filtering/classification API

2016-10-10 Thread Zhao1, Wei
{ uint32_t id; /**< 32 bit value to return with packets. */ }; > -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Adrien Mazarguil > Sent: Saturday, August 20, 2016 3:33 AM > To: dev at dpdk.org > Subject: [dpdk-dev] [RFC v2] Gen

[dpdk-dev] [RFC v2] Generic flow director/filtering/classification API

2016-08-22 Thread John Fastabend
On 16-08-19 12:32 PM, Adrien Mazarguil wrote: > Hi All, > > Thanks to many for the positive and constructive feedback I've received so > far. Here is the updated specification (v0.7) at last. > > I've attempted to address as many comments as possible but could not > process them all just yet. A

[dpdk-dev] [RFC v2] Generic flow director/filtering/classification API

2016-08-19 Thread Adrien Mazarguil
Hi All, Thanks to many for the positive and constructive feedback I've received so far. Here is the updated specification (v0.7) at last. I've attempted to address as many comments as possible but could not process them all just yet. A new section "Future evolutions" has been added for the