From: James Huang <jamsphon@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Intel I350 igb PMD VLAN offload transmition issue?
Date: Thu, 1 Mar 2018 16:35:57 -0800 [thread overview]
Message-ID: <CAFpuyR4ox=j7a7jHrQsh3aXvfEWe-DX1Azqx_yLaUCTeny+UxA@mail.gmail.com> (raw)
Hello,
We're experiencing PMD VLAN offload transmition issue on Intel I350
[8086:1521] NIC.
OS: CentOS 6.5 x64
DPDK 17.05.2
NIC firmware check with Linux ethtool, firmware-version: 1.67, 0x80000dd0,
17.5.10
The VLAN offload receiving portion works fine, could get mbuf
ol_flags=0x1c1, with correct vlan_tci value.
However, on sending time, when set mbuf ol_flags=0x200000000000000 and
vlan_tci value, there is no packet going out on the wire. in the meantime,
dpdk-pdump tool could capture the outgoing packet without vlan tagging.
This issue does not happen if switch the NIC from I350 to X540 10G
interface.
And, if does not use VLAN, I350 works fine, too.
Is the I350 NIC hardware compatible issue, or something else?
Is possible to fix the issue?
Regards,
James Huang
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
reply other threads:[~2018-03-02 0:36 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='CAFpuyR4ox=j7a7jHrQsh3aXvfEWe-DX1Azqx_yLaUCTeny+UxA@mail.gmail.com' \
--to=jamsphon@gmail.com \
--cc=users@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).