From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: Caianning <caianning@huawei.com>,
"users@dpdk.org" <users@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] HOW to forward vlan pkt using DPDK loadbalancer and L2FD, with intel 82599ES
Date: Fri, 4 Nov 2016 05:19:41 +0000 [thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09093934108A@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <F994AE62EFA2864BAC5A2B81D86C27C13E2D85E9@nkgeml514-mbx.china.huawei.com>
Hi Anning,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Caianning
> Sent: Friday, November 4, 2016 10:51 AM
> To: users@dpdk.org; dev@dpdk.org
> Subject: [dpdk-dev] HOW to forward vlan pkt using DPDK loadbalancer and L2FD,
> with intel 82599ES
>
> HI,
>
> I am using DPDK 16.07 example loadbalancer to as LB to forward vlan pkt
> to applications. LB and applications are using VFs bound with DPDK igb_uio
> driver.
> But I found the packet can not be send from LB to application. Pkt input to LB
> with vlan, after LB processing it is sent out to application using another VF.
>
> As 82599 need vlan filters if we use VF to process vlan pkts, in the LB we called
> rte api to add a vlan filter and enable vlan flilter. And set port_conf with vlan
> strip off.
> And for the application(L2FWD) we use the cmd: ip link set PFxxx VF yy vlan
> VLANID.
>
> In the LB ,we can receive pkts with vlan, after processing(cut the head and add
> another L2 head with same vlan tag, set destination MAC to application VF), it is
> send out to the application VF.
> the result is: LB can still processing ,but all the pkt post.
>
> We also did an experiment using testPMD to forward vlan pkt to application on
> the same VF used by LB, and it is OK.
> We tried kinds of different set of vlan filter, vlan strip, ip link set, but found no
> solution.
>
> Does anyone meet the similar problem? And what factor casued the difference?
>
> Thx.
I saw you mentioned testpmd is fine. Testpmd is a very simple example, normally it forwards packets blindly. It means there's no route rule. It just forwards packets from one port to another.
I guess the difference is the APP you use has some rules for routing/swithing.
prev parent reply other threads:[~2016-11-04 5:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 2:51 Caianning
2016-11-04 5:19 ` Lu, Wenzhuo [this message]
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=6A0DE07E22DDAD4C9103DF62FEBC09093934108A@shsmsx102.ccr.corp.intel.com \
--to=wenzhuo.lu@intel.com \
--cc=caianning@huawei.com \
--cc=dev@dpdk.org \
--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).