DPDK patches and discussions
 help / color / mirror / Atom feed
From: 韩爽 <hanshuang@qianxin.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: ice QinQ Offload not working on DPDK 21.11.1
Date: Fri, 8 Jul 2022 02:46:33 +0000	[thread overview]
Message-ID: <365f258779af4d8fbde856392fe94984@qianxin.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]

Hello,

We recently tested QINQ offload for intel E810 nic. [Ethernet controller: Intel Corporation Ethernet Controller E810-C for SFP (rev 02) Device id 8086:1593]
relative software versions as below:
DPDK: 21.11.1
kernel driver: 1.7.16
OS default DDP: 1.3.27
Firmware: 3.1

We've tested testpmd and the offload setting as below:
struct rte_eth_rxmode rx_mode = {
.offloads = DEV_RX_OFFLOAD_VLAN_EXTEND | DEV_RX_OFFLOAD_VLAN_STRIP | DEV_RX_OFFLOAD_QINQ_STRIP | DEV_RX_OFFLOAD_RSS_HASH,
};

struct rte_eth_txmode tx_mode = {
.offloads = RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE | RTE_ETH_TX_OFFLOAD_VLAN_INSERT | RTE_ETH_TX_OFFLOAD_QINQ_INSERT,
};

We use traffic gen some QINQ packet with double vlan tag 0x8100,
on rx side: the outer vlan tag has been stripped, but the inner vlan tag not, mbuf->vlan_tci_outer is 0, ol_flags: RTE_MBUF_F_RX_VLAN RTE_MBUF_F_RX_L4_CKSUM_GOOD RTE_MBUF_F_RX_IP_CKSUM_GOOD RTE_MBUF_F_RX_VLAN_STRIPPED RTE_MBUF_F_RX_OUTER_L4_CKSUM_UNKNOWN
on tx side: we modified testpmd code, force to insert double vlan, mbuf->vlan_tci_outer = 101; mbuf->vlan_tci = 201; the outer vlan tag (mbuf->vlan_tci_outer) lost, packet send out by testpmd only have one vlan tag (201), ol_flags: RTE_MBUF_F_TX_VLAN | RTE_MBUF_F_TX_QINQ

I believe this is a bug at the NVM firmware level or DDP package but still want someone else to confirm. We are trying to reach out to Intel as well to report the issue and get additional assistance. If anyone can assist with that, it would be appreciated.


韩爽
鲲鹏网络平台部门

北京奇安信集团
Beijing Qi An Xin Group

手机 +86 18600206283
邮箱 hanshuang@qianxin.com<mailto:hanshuang@qianxin.com>


[-- Attachment #2: Type: text/html, Size: 5867 bytes --]

                 reply	other threads:[~2022-07-08  2:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=365f258779af4d8fbde856392fe94984@qianxin.com \
    --to=hanshuang@qianxin.com \
    --cc=dev@dpdk.org \
    /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).