* [dpdk-dev] How about add rte flow get capablity APIs
@ 2021-03-23 0:52 Fengchengwen
2021-03-23 10:27 ` Ferruh Yigit
0 siblings, 1 reply; 3+ messages in thread
From: Fengchengwen @ 2021-03-23 0:52 UTC (permalink / raw)
To: orika, ferruh.yigit; +Cc: dev, humin (Q)
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] How about add rte flow get capablity APIs
2021-03-23 0:52 [dpdk-dev] How about add rte flow get capablity APIs Fengchengwen
@ 2021-03-23 10:27 ` Ferruh Yigit
2021-03-24 0:44 ` fengchengwen
0 siblings, 1 reply; 3+ messages in thread
From: Ferruh Yigit @ 2021-03-23 10:27 UTC (permalink / raw)
To: Fengchengwen, orika; +Cc: dev, humin (Q), Thomas Monjalon, Andrew Rybchenko
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] How about add rte flow get capablity APIs
2021-03-23 10:27 ` Ferruh Yigit
@ 2021-03-24 0:44 ` fengchengwen
0 siblings, 0 replies; 3+ messages in thread
From: fengchengwen @ 2021-03-24 0:44 UTC (permalink / raw)
To: Ferruh Yigit, orika; +Cc: dev, humin (Q), Thomas Monjalon, Andrew Rybchenko
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-03-24 0:44 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-23 0:52 [dpdk-dev] How about add rte flow get capablity APIs Fengchengwen
2021-03-23 10:27 ` Ferruh Yigit
2021-03-24 0:44 ` fengchengwen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).