[dpdk-dev] VLAN header insertion and removal

[dpdk-dev] VLAN header insertion and removal

[Padam Jeet Singh]

Hello,

I have done a simple mbuf adjust and prepend to achieve the removal and insertion of the vlan header and it works fine. The use case is something similar to the l3fwd example where one port has traffic coming in on multiple vlans and the other port has no vlans. The packet processing path in the middle inserts or removes the vlan.

Is there an offload flag or mode where this can be done in hardware? Or is there a more optimized way to do this in dpdk? For sake of performance I want to avoid the copy ethernet header, modify mbuf, copy back the header steps.

Thanks,
Padam
---------------------------
Sent from my mobile. Please excuse the brevity, spelling and punctuation.

Re: [dpdk-dev] VLAN header insertion and removal

[Alex Markuze]

On ingress when configuring the device
                                        1.modify
the rte_eth_conf.rxmode.hw_vlan_strip  = 1,

On egress you need to  modify the rte_van_macip struct in the sent mbuf*.
(rte_mbuf.h)
                                       1. add the PKT_TX_VLAN_PKT to the
ol_flags fields.
                                       2. fill the plan_tci in
pkt.vlan_macip.f.vlan_tci

*This is true for dpdk 1.7, structs may have moved in 1.8

On Sat, Dec 20, 2014 at 8:39 PM, Padam Jeet Singh <padam.singh@inventum.net>
wrote:

> Hello,
>
> I have done a simple mbuf adjust and prepend to achieve the removal and
> insertion of the vlan header and it works fine. The use case is something
> similar to the l3fwd example where one port has traffic coming in on
> multiple vlans and the other port has no vlans. The packet processing path
> in the middle inserts or removes the vlan.
>
> Is there an offload flag or mode where this can be done in hardware? Or is
> there a more optimized way to do this in dpdk? For sake of performance I
> want to avoid the copy ethernet header, modify mbuf, copy back the header
> steps.
>
> Thanks,
> Padam
> ---------------------------
> Sent from my mobile. Please excuse the brevity, spelling and punctuation.
>
>

Re: [dpdk-dev] VLAN header insertion and removal

[Padam J. Singh]

Hello Alex,

Thanks for the help - this worked!

BR,
Padam

> On 21-Dec-2014, at 2:42 pm, Alex Markuze <alex@weka.io> wrote:
> 
> On ingress when configuring the device 
>                                         1.modify the rte_eth_conf.rxmode.hw_vlan_strip  = 1,
> 
> On egress you need to  modify the rte_van_macip struct in the sent mbuf*. (rte_mbuf.h)
>                                        1. add the PKT_TX_VLAN_PKT to the ol_flags fields.
>                                        2. fill the plan_tci in pkt.vlan_macip.f.vlan_tci 
> 
> *This is true for dpdk 1.7, structs may have moved in 1.8
> 
> On Sat, Dec 20, 2014 at 8:39 PM, Padam Jeet Singh <padam.singh@inventum.net <mailto:padam.singh@inventum.net>> wrote:
> Hello,
> 
> I have done a simple mbuf adjust and prepend to achieve the removal and insertion of the vlan header and it works fine. The use case is something similar to the l3fwd example where one port has traffic coming in on multiple vlans and the other port has no vlans. The packet processing path in the middle inserts or removes the vlan.
> 
> Is there an offload flag or mode where this can be done in hardware? Or is there a more optimized way to do this in dpdk? For sake of performance I want to avoid the copy ethernet header, modify mbuf, copy back the header steps.
> 
> Thanks,
> Padam
> ---------------------------
> Sent from my mobile. Please excuse the brevity, spelling and punctuation.
> 
> 

 Padam J. Singh | VP Engg. | Inventum Technologies Private Limited
www.inventum.net <http://www.inventum.net/>
+91.9810146640
 
Address:
C-70, Phase II Extension,
Noida 201305, UP,
India
 
Tel     : +91.120.4647000
 
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. No employee or agent is authorized to conclude any binding agreement on behalf of [Inventum Technologies Private Limited] with another party by email without express written confirmation by a whole-time Director of the Company who has been authorized vide a valid board resolution to the effect. Our company accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Employees of [Inventum Technologies Private Limited] are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to company policy and outside the scope of the employment of the individual concerned. The company will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising.