On 11/4/2020 1:28 PM, Matan Azrad wrote:
From: Ferruh Yigit
On 11/3/2020 7:33 AM, Matan Azrad wrote:
Hi Ferruh
Thank you for the fast review.
Please see inline
From: Ferruh Yigit
On 11/1/2020 5:48 PM, Matan Azrad wrote:
When an age action becomes aged-out the rte_flow_get_aged_flows
sho
From: Ferruh Yigit
> On 11/3/2020 7:33 AM, Matan Azrad wrote:
> > Hi Ferruh
> >
> > Thank you for the fast review.
> > Please see inline
> >
> > From: Ferruh Yigit
> >> On 11/1/2020 5:48 PM, Matan Azrad wrote:
> >>> When an age action becomes aged-out the rte_flow_get_aged_flows
> >>> should ret
On 11/3/2020 7:33 AM, Matan Azrad wrote:
Hi Ferruh
Thank you for the fast review.
Please see inline
From: Ferruh Yigit
On 11/1/2020 5:48 PM, Matan Azrad wrote:
When an age action becomes aged-out the rte_flow_get_aged_flows should
return the action context supplied by the configuration struct
Hi Ferruh
Thank you for the fast review.
Please see inline
From: Ferruh Yigit
> On 11/1/2020 5:48 PM, Matan Azrad wrote:
> > When an age action becomes aged-out the rte_flow_get_aged_flows should
> > return the action context supplied by the configuration structure.
> >
> > In case the age action
On 11/1/2020 5:48 PM, Matan Azrad wrote:
When an age action becomes aged-out the rte_flow_get_aged_flows should
return the action context supplied by the configuration structure.
In case the age action created by the shared action API, the shared
action context of the Testpmd application was not
When an age action becomes aged-out the rte_flow_get_aged_flows should
return the action context supplied by the configuration structure.
In case the age action created by the shared action API, the shared
action context of the Testpmd application was not set.
In addition, the application handler
6 matches
Mail list logo
