On 10/30/16 at 06:28pm, Tom Herbert wrote: > Right, that's why we rely on a dst cache. Any use of LWT that > encapsulates or tunnels to a fixed destination (ILA, VXLAN, IPIP, > etc.) would want to use the dst cache optimization to avoid the second > lookup. The ILA LWT code used to call orig output and that worked as > long as we could set the default router as the gateway "via". It was > something we were able to deploy, but not a general solution. > Integrating properly with routing gives a much better solution IMO. > Note that David Lebrun's latest LWT Segment Routing patch does the > second lookup with the dst cache to try to avoid it.
Noticed while implementing this: How does ILA ensure that dst_output() is not invoked in a circular manner? dstA->output() -> dstB->otuput() -> dstA->output() -> ...
