Hi, Ori and Ferruh Currently, the rte flow APIs lack of get capability APIs, upper-application could not get the device capability unless look doc or code or even test it. Maybe it's a good idea to add the get capability like traffic manager framework, what do you think? Regards
On 3/23/2021 12:52 AM, Fengchengwen wrote:
> Hi, Ori and Ferruh
>
> Currently, the rte flow APIs lack of get capability APIs, upper-application
>
> could not get the device capability unless look doc or code or even test it.
>
> Maybe it's a good idea to add the get capability like traffic manager
>
> framework, what do you think?
>
Not providing capability was a design decision, because it may not be possible
to provide capability information correctly.
The preferred method is 'rte_flow_validate()'.
Application should call 'rte_flow_validate()' to decide if a rule can be created
or not, and take an action accordingly.
On 2021/3/23 18:27, Ferruh Yigit wrote:
> On 3/23/2021 12:52 AM, Fengchengwen wrote:
>> Hi, Ori and Ferruh
>>
>> Currently, the rte flow APIs lack of get capability APIs, upper-application
>>
>> could not get the device capability unless look doc or code or even test it.
>>
>> Maybe it's a good idea to add the get capability like traffic manager
>>
>> framework, what do you think?
>>
>
> Not providing capability was a design decision, because it may not be possible to provide capability information correctly.
>
> The preferred method is 'rte_flow_validate()'.
> Application should call 'rte_flow_validate()' to decide if a rule can be created or not, and take an action accordingly.
>
> .
Got it, Thank you, Ferruh