From: Beilei Xing <beilei.xing@intel.com>
To: qi.z.zhang@intel.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2] net/i40e: allow VF to configure pctype mapping
Date: Thu, 23 May 2019 09:37:14 +0800 [thread overview]
Message-ID: <1558575434-57309-1-git-send-email-beilei.xing@intel.com> (raw)
In-Reply-To: <1558506891-8427-1-git-send-email-beilei.xing@intel.com>
This patch allows VF to get/update/reset pctype
mapping info.
Signed-off-by: Beilei Xing <beilei.xing@intel.com>
---
v2 changes:
- Allow VF update/reset pctype mapping.
drivers/net/i40e/rte_pmd_i40e.c | 8 --------
1 file changed, 8 deletions(-)
diff --git a/drivers/net/i40e/rte_pmd_i40e.c b/drivers/net/i40e/rte_pmd_i40e.c
index 7ae78e4..b3bdc61 100644
--- a/drivers/net/i40e/rte_pmd_i40e.c
+++ b/drivers/net/i40e/rte_pmd_i40e.c
@@ -2405,8 +2405,6 @@ int rte_pmd_i40e_flow_type_mapping_reset(uint16_t port)
dev = &rte_eth_devices[port];
- if (!is_i40e_supported(dev))
- return -ENOTSUP;
i40e_set_default_pctype_table(dev);
@@ -2425,9 +2423,6 @@ int rte_pmd_i40e_flow_type_mapping_get(
dev = &rte_eth_devices[port];
- if (!is_i40e_supported(dev))
- return -ENOTSUP;
-
ad = I40E_DEV_PRIVATE_TO_ADAPTER(dev->data->dev_private);
for (i = 0; i < I40E_FLOW_TYPE_MAX; i++) {
@@ -2453,9 +2448,6 @@ rte_pmd_i40e_flow_type_mapping_update(
dev = &rte_eth_devices[port];
- if (!is_i40e_supported(dev))
- return -ENOTSUP;
-
if (count > I40E_FLOW_TYPE_MAX)
return -EINVAL;
--
2.5.5
next prev parent reply other threads:[~2019-05-23 1:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 6:34 [dpdk-dev] [PATCH] net/i40e: allow VF to get pctype mapping info Beilei Xing
2019-05-23 1:37 ` Beilei Xing [this message]
2019-05-24 13:52 ` [dpdk-dev] [PATCH v2] net/i40e: allow VF to configure pctype mapping Ferruh Yigit
2019-05-27 16:36 ` Zhang, Qi Z
2019-06-12 7:10 ` [dpdk-dev] [PATCH v3] " Beilei Xing
2019-06-17 3:17 ` [dpdk-dev] [PATCH v4] " Beilei Xing
2019-06-18 13:14 ` Zhang, Qi Z
2019-06-18 13:16 ` Zhang, Qi Z
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=1558575434-57309-1-git-send-email-beilei.xing@intel.com \
--to=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.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).