From: fengchengwen <fengchengwen@huawei.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
"orika@nvidia.com" <orika@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "humin (Q)" <humin29@huawei.com>,
"Thomas Monjalon" <thomas@monjalon.net>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [dpdk-dev] How about add rte flow get capablity APIs
Date: Wed, 24 Mar 2021 08:44:41 +0800 [thread overview]
Message-ID: <7b4e9585-2ca2-f4cd-afce-499b4c3f8633@huawei.com> (raw)
In-Reply-To: <8a6224ba-301e-d5a2-d515-265b3bf1b97d@intel.com>
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
prev parent reply other threads:[~2021-03-24 0:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 0:52 Fengchengwen
2021-03-23 10:27 ` Ferruh Yigit
2021-03-24 0:44 ` fengchengwen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7b4e9585-2ca2-f4cd-afce-499b4c3f8633@huawei.com \
--to=fengchengwen@huawei.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=humin29@huawei.com \
--cc=orika@nvidia.com \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).