Appreciate the l2-input feature arch tip.  Even when I use only device-input 
and interface-output,  I still use VPP's vector processing.  I wrote a 5G UPF 
VPP plugin (uses 6-tuple) this way and see packet performance comparable to 
stateful and deterministic NAT44 VPP plugin.  A 5G UPF does lot more than the 
deterministic NAT44.  Travelping has a UPF VPP plugin but I couldn't get their 
code to install and work to compare performance.

I didn't look hard, but I don't see a tuple hash in VPP as described in this 
paper: https://tinyurl.com/y5p5resg.  The plugin I wrote uses the tuple hash of 
the paper.

Hemant

-----Original Message-----
From: Damjan Marion <dmar...@me.com> 
Sent: Friday, November 20, 2020 12:20 PM
To: hem...@mnkcg.com
Cc: 叶东岗 <y...@wangsu.com>; Neale Ranns <nra...@cisco.com>; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] why tunnel interfaces do not support device-input 
feature?



> On 20.11.2020., at 17:16, hemant via lists.fd.io 
> <hemant=mnkcg....@lists.fd.io> wrote:
> 
> Please see in line below against "<hs>".
> 
> -----Original Message-----
> From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Damjan 
> Marion via lists.fd.io
> Sent: Friday, November 20, 2020 3:45 AM
> To: hem...@mnkcg.com
> Cc: y...@wangsu.com; Neale Ranns <nra...@cisco.com>; 
> vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] why tunnel interfaces do not support 
> device-input feature?
> 
> Is your encap L2 or L3 ? do you transport ethernet header or just ip4/ip6?
> 
> <hs> L2
> 
> What is your criteria for selecting packets to be encapsulated? any 
> ethernet frame, particular VLAN, Q-in-Q, Ip4/6 address?
> 
> <hs> layer-3 information + layer-4 ports (5-tuple).  The 5-tuple is 
> looked up from packet and a tunnel id (teid) is returned.
> 
> How  do you want to assign L2 DMAC of the next hop device before 
> sending encapsulated packet out of the interface?
> 
> <hs> An egress table consists of teid vs. dmac.  This table lookup 
> provides dmac. Just use device-input arc for packet ingress and 
> interface-output for packet egress.
> 
> Also, thanks to Ben for replying.

Based on what you are explaining here, you don't need  much from VPP.
You can do int simpler and faster simply by writing small DPDK application.

In VPP such thing can be achieved by using l2-input feature arch. You just need 
to switch interface to L2 mode and you wiill get all ethernet frames there, 
v4,v6 ucast and mcast….

—
Damjan

Attachment: smime.p7s
Description: S/MIME cryptographic signature

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18111): https://lists.fd.io/g/vpp-dev/message/18111
Mute This Topic: https://lists.fd.io/mt/78307484/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to