From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Martin Havlik <xhavli56@stud.fit.vutbr.cz>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
"Min Hu (Connor)" <humin29@huawei.com>,
Xueming Li <xuemingl@nvidia.com>, Bing Zhao <bingz@nvidia.com>,
Chengchang Tang <tangchengchang@huawei.com>,
Jan Viktorin <viktorin@cesnet.cz>, dpdk-dev <dev@dpdk.org>,
Chas Williams <chas3@att.com>,
Haiyue Wang <haiyue.wang@intel.com>,
Ivan Ilchenko <ivan.ilchenko@oktetlabs.ru>,
Singh Aman Deep <aman.deep.singh@intel.com>,
kirankn@juniper.net, lirongqing@baidu.com
Subject: Re: [dpdk-dev] [PATCH 1/2] lib/ethdev: introduce RTE_ETH_DEV_CAPA_FLOW_CREATE_BEFORE_START
Date: Wed, 6 Oct 2021 10:13:11 -0700 [thread overview]
Message-ID: <CACZ4nhsPzz+NacbuiEL=Nuudm4KTO99ZExRv89uj94T1hGsxbw@mail.gmail.com> (raw)
In-Reply-To: <20211005171914.2936-1-xhavli56@stud.fit.vutbr.cz>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
On Tue, Oct 5, 2021 at 10:29 AM Martin Havlik
<xhavli56@stud.fit.vutbr.cz> wrote:
>
> Not all PMDs allow RTE flow rules to be created before start.
> This capability will be set for the ones that allow it.
>
> Signed-off-by: Martin Havlik <xhavli56@stud.fit.vutbr.cz>
Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> ---
> lib/ethdev/rte_ethdev.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/lib/ethdev/rte_ethdev.h b/lib/ethdev/rte_ethdev.h
> index bef24173cf..3115a6fccf 100644
> --- a/lib/ethdev/rte_ethdev.h
> +++ b/lib/ethdev/rte_ethdev.h
> @@ -1448,6 +1448,8 @@ struct rte_eth_conf {
> #define RTE_ETH_DEV_CAPA_RUNTIME_RX_QUEUE_SETUP 0x00000001
> /** Device supports Tx queue setup after device started. */
> #define RTE_ETH_DEV_CAPA_RUNTIME_TX_QUEUE_SETUP 0x00000002
> +/** Device supports RTE Flow rule creation before device start. */
> +#define RTE_ETH_DEV_CAPA_FLOW_CREATE_BEFORE_START 0x00000004
> /**@}*/
>
> /*
> --
> 2.27.0
>
next prev parent reply other threads:[~2021-10-06 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 17:19 Martin Havlik
2021-10-06 17:13 ` Ajit Khaparde [this message]
2021-10-12 12:02 ` Andrew Rybchenko
2022-09-26 14:38 ` Thomas Monjalon
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='CACZ4nhsPzz+NacbuiEL=Nuudm4KTO99ZExRv89uj94T1hGsxbw@mail.gmail.com' \
--to=ajit.khaparde@broadcom.com \
--cc=aman.deep.singh@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bingz@nvidia.com \
--cc=chas3@att.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=haiyue.wang@intel.com \
--cc=humin29@huawei.com \
--cc=ivan.ilchenko@oktetlabs.ru \
--cc=kirankn@juniper.net \
--cc=lirongqing@baidu.com \
--cc=tangchengchang@huawei.com \
--cc=thomas@monjalon.net \
--cc=viktorin@cesnet.cz \
--cc=xhavli56@stud.fit.vutbr.cz \
--cc=xuemingl@nvidia.com \
/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).