From: Tal Shnaiderman <talshn@nvidia.com>
To: <dev@dpdk.org>
Cc: <thomas@monjalon.net>, <matan@nvidia.com>, <rasland@nvidia.com>,
<asafp@nvidia.com>, <viacheslavo@nvidia.com>, <eilong@nvidia.com>,
<kcollins@nvidia.com>, <idanhac@nvidia.com>
Subject: [dpdk-dev] [RFC PATCH 10/12] net/mlx5: support VLAN stripping offload on Windows
Date: Wed, 15 Sep 2021 13:43:46 +0300 [thread overview]
Message-ID: <20210915104348.12920-11-talshn@nvidia.com> (raw)
In-Reply-To: <20210915104348.12920-1-talshn@nvidia.com>
Support of the VLAN stripping offloading by checking
the relevant FW capability (vlan_cap) for NIC support.
Supported offload:
DEV_RX_OFFLOAD_VLAN_STRIP
Signed-off-by: Tal Shnaiderman <talshn@nvidia.com>
---
drivers/net/mlx5/windows/mlx5_os.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/net/mlx5/windows/mlx5_os.c b/drivers/net/mlx5/windows/mlx5_os.c
index 2aaacd0afb..4d4a7c19ac 100644
--- a/drivers/net/mlx5/windows/mlx5_os.c
+++ b/drivers/net/mlx5/windows/mlx5_os.c
@@ -475,8 +475,6 @@ mlx5_dev_spawn(struct rte_device *dpdk_dev,
config->ind_table_max_size = ETH_RSS_RETA_SIZE_512;
DRV_LOG(DEBUG, "maximum Rx indirection table size is %u",
config->ind_table_max_size);
- DRV_LOG(DEBUG, "VLAN stripping is %ssupported",
- (config->hw_vlan_strip ? "" : "not "));
if (config->hw_padding) {
DRV_LOG(DEBUG, "Rx end alignment padding isn't supported");
config->hw_padding = 0;
@@ -510,6 +508,9 @@ mlx5_dev_spawn(struct rte_device *dpdk_dev,
config->hw_csum = config->hca_attr.csum_cap;
DRV_LOG(DEBUG, "checksum offloading is %ssupported",
(config->hw_csum ? "" : "not "));
+ config->hw_vlan_strip = config->hca_attr.vlan_cap;
+ DRV_LOG(DEBUG, "VLAN stripping is %ssupported",
+ (config->hw_vlan_strip ? "" : "not "));
}
if (config->devx) {
uint32_t reg[MLX5_ST_SZ_DW(register_mtutc)];
--
2.16.1.windows.4
next prev parent reply other threads:[~2021-09-15 10:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 10:43 [dpdk-dev] [RFC PATCH 00/12] Expand NIC offloads support " Tal Shnaiderman
2021-09-15 10:43 ` [dpdk-dev] [RFC PATCH 01/12] net/mlx5: fix software parsing support query Tal Shnaiderman
2021-09-15 10:43 ` [dpdk-dev] [RFC PATCH 02/12] common/mlx5: read software parsing capabilities from DevX Tal Shnaiderman
2021-09-15 10:43 ` [dpdk-dev] [RFC PATCH 03/12] net/mlx5: query software parsing support on Windows Tal Shnaiderman
2021-09-15 10:43 ` [dpdk-dev] [RFC PATCH 04/12] net/mlx5: fix tunneling support query Tal Shnaiderman
2021-09-15 10:43 ` [dpdk-dev] [RFC PATCH 05/12] common/mlx5: read tunneling capabilities from DevX Tal Shnaiderman
2021-09-15 10:43 ` [dpdk-dev] [RFC PATCH 06/12] net/mlx5: query tunneling support on Windows Tal Shnaiderman
2021-09-15 10:43 ` [dpdk-dev] [RFC PATCH 07/12] common/mlx5: read TSO capability from DevX Tal Shnaiderman
2021-09-15 10:43 ` [dpdk-dev] [RFC PATCH 08/12] net/mlx5: support TSO offload on Windows Tal Shnaiderman
2021-09-15 10:43 ` [dpdk-dev] [RFC PATCH 09/12] common/mlx5: read VLAN capability from DevX Tal Shnaiderman
2021-09-15 10:43 ` Tal Shnaiderman [this message]
2021-09-15 10:43 ` [dpdk-dev] [RFC PATCH 11/12] common/mlx5: read FCS scattering " Tal Shnaiderman
2021-09-15 10:43 ` [dpdk-dev] [RFC PATCH 12/12] net/mlx5: support keep-CRC offload on Windows Tal Shnaiderman
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=20210915104348.12920-11-talshn@nvidia.com \
--to=talshn@nvidia.com \
--cc=asafp@nvidia.com \
--cc=dev@dpdk.org \
--cc=eilong@nvidia.com \
--cc=idanhac@nvidia.com \
--cc=kcollins@nvidia.com \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@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).