From: "Zhao1, Wei" <wei.zhao1@intel.com>
To: 1534898891 <1534898891@qq.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] dpdk vlan strip offload bug for I350 nic?
Date: Tue, 18 Dec 2018 02:26:32 +0000 [thread overview]
Message-ID: <A2573D2ACFCADC41BB3BE09C6DE313CA07E8C1B1@PGSMSX103.gar.corp.intel.com> (raw)
In-Reply-To: <tencent_6295556D7623DCA43934B1E1C12A5E60D805@qq.com>
Hi,
We can not get your attachment at all.
VLAN STRIP is done by hardware NIC, not DPDK software.
BUT you can check the flag of packets output from rte_eth_rx_burst(),
Check bit of PKT_RX_VLAN in rxm->ol_flags. Only if this bit is set rxm->vlan_tci is valid.
For IMCP packet, maybe it is not set at all.
BTW, please give out the predicted and actual vlan_tci to us for debug.
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of 1534898891
> Sent: Sunday, December 9, 2018 1:23 PM
> To: dev <dev@dpdk.org>
> Subject: Re: [dpdk-dev] dpdk vlan strip offload bug for I350 nic?
>
> My server's port connect to switch with trunk. The gw IP on switch's vlan-if. I
> used kni send icmp reques to gw, but the vlan_tci of icmp reply packets is
> incorrect. Other packets are correct. such as the ping same subnet servers or
> other packets(tcp or udp) and switch gw ping my kni is OK. This is too weird.
> The attachment is my test program. I guess it's dpdk drive bug or firmware
> bug.
>
>
> Any help is appreciated.
>
>
> Thanks.
>
>
>
> ------------------ Original ------------------
> From: "冰泪"<1534898891@qq.com>;
> Date: Sun, Dec 9, 2018 12:30 PM
> To: "dev"<dev@dpdk.org>;
>
> Subject: dpdk vlan strip offload bug for I350 nic?
>
>
>
> Hi Guys:
> I used the vlan strip offload in I350 nic case. VLAN tag is incorrect when
> packets are ICMP. Other packets are correct.
> NIC:I350
> DPDK version:18.02 OS:centos 7.4
> Any help is appreciated.
>
>
> Thanks.
> Hongbowang.
next prev parent reply other threads:[~2018-12-18 2:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-09 4:30 1534898891
2018-12-09 5:23 ` =?gb18030?B?MTUzNDg5ODg5MQ==?=
2018-12-18 2:26 ` Zhao1, Wei [this message]
2018-12-10 7:53 ` [dpdk-dev] rte_eal_hotplug_remove() generates error message Hideyuki Yamashita
2018-12-11 0:54 ` Hideyuki Yamashita
2018-12-17 10:02 ` Hideyuki Yamashita
2018-12-17 10:23 ` Burakov, Anatoly
2018-12-17 10:38 ` Burakov, Anatoly
2018-12-17 11:03 ` Hideyuki Yamashita
2018-12-17 10:45 ` Hideyuki Yamashita
2018-12-17 11:21 ` Burakov, Anatoly
2018-12-17 12:10 ` Hideyuki Yamashita
2018-12-18 2:39 ` Tiwei Bie
2018-12-18 3:11 ` Hideyuki Yamashita
2018-12-18 5:12 ` Tiwei Bie
2018-12-18 5:52 ` Hideyuki Yamashita
2018-12-18 6:25 ` Tiwei Bie
2018-12-18 11:30 ` Hideyuki Yamashita
2018-12-18 13:09 ` Tiwei Bie
2018-12-27 5:52 ` Hideyuki Yamashita
2019-01-02 9:19 ` Tiwei Bie
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=A2573D2ACFCADC41BB3BE09C6DE313CA07E8C1B1@PGSMSX103.gar.corp.intel.com \
--to=wei.zhao1@intel.com \
--cc=1534898891@qq.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).