diff options
| author |   John Lo <loj@cisco.com> | 2016-11-07 18:30:47 -0500 |
|---|---|---|
| committer |   Damjan Marion <dmarion.lists@gmail.com> | 2016-11-10 12:45:00 +0000 |
| commit | c42912de8e2873c6a107fee047773b13950a764b (patch) | |
| tree | 56fffe89680f81df4dfe05aa536dd17a424fa04e /vpp-api/java/m4/ax_prog_java_works.m4 | |
| parent | 450cd302ee58887d824810d3b940d5d9febd0cf1 (diff) | |
VXLAN tunnel encap forwarding optimization with FIB 2.0
Optimize VXLAN encap node so that vxlan4-encap node is used for IP4
and vxlan6-encap node is used for IP6 underlay. Also stack the VXLAN
encap nodes to the appropriate FIB IP4 or IP6 load-balance node
instead of ip4/ip6-lookup node to save IP lookup operation.
For VXLAN decap node, check VXLAN header FLAGS field for each packet
and remove the code to support decap-next for IP4 or IP6. These decap-
next values were intended for experimentation purposes and not needed
any more since VXLAN-GPE tunnel is supported. The decap-next field is
still kept in API for backward compatibility and its value has no
effect. Decap next for both vxlan4-decap and vxlan6-decap nodes is
always l2-input node.
Change-Id: I8ac95774946549ec403ab691f999df0c006b460f
Signed-off-by: John Lo <loj@cisco.com>
Diffstat (limited to 'vpp-api/java/m4/ax_prog_java_works.m4')
0 files changed, 0 insertions, 0 deletions