From: Martin Havlik <xhavli56@stud.fit.vutbr.cz>
To: xhavli56@stud.fit.vutbr.cz
Cc: Jan Viktorin <viktorin@cesnet.cz>,
dev@dpdk.org, chas3@att.com, humin29@huawei.com,
ferruh.yigit@intel.com, thomas@monjalon.net,
andrew.rybchenko@oktetlabs.ru, haiyue.wang@intel.com,
ivan.ilchenko@oktetlabs.ru, aman.deep.singh@intel.com,
kirankn@juniper.net, lirongqing@baidu.com,
ajit.khaparde@broadcom.com
Subject: [dpdk-dev] [PATCH 0/2] net/bonding: fix dedicated queues flow rule issue
Date: Tue, 5 Oct 2021 19:16:11 +0200 [thread overview]
Message-ID: <20211005171613.2879-1-xhavli56@stud.fit.vutbr.cz> (raw)
This patchset stems from [1].
Not all PMDs allow RTE flow rule creation before device start.
Introduced capability marks the ones that allow it.
The capability is then used to fix flow rule creation for
dedicated queues in slave devices in bonding.
The introduced capa _will need to be set_ for all appropriate PMDs
in `rte_eth_dev_info->dev_capa`.
That is not pretty, but it holds the semantics of a capability
correctly, as opposed to making it a requirement to have the device
started before creating flow rules.
[1] https://www.mail-archive.com/dev@dpdk.org/msg214840.html
Martin Havlik (2):
lib/ethdev: introduce RTE_ETH_DEV_CAPA_FLOW_CREATE_BEFORE_START
net/bonding: require started device for dedicated queues
drivers/net/bonding/rte_eth_bond_pmd.c | 25 +++++++++++++++++++------
lib/ethdev/rte_ethdev.h | 2 ++
2 files changed, 21 insertions(+), 6 deletions(-)
--
2.27.0
next reply other threads:[~2021-10-05 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 17:16 Martin Havlik [this message]
2021-10-27 9:55 ` Ferruh Yigit
2021-11-07 11:03 ` Havlík Martin
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=20211005171613.2879-1-xhavli56@stud.fit.vutbr.cz \
--to=xhavli56@stud.fit.vutbr.cz \
--cc=ajit.khaparde@broadcom.com \
--cc=aman.deep.singh@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--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=thomas@monjalon.net \
--cc=viktorin@cesnet.cz \
/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).