Cool. Next time you have time, please go ahead and make the change.
I’m planning to use the L2 classify path in a use-case which would never be enabled at the same time as the ACL plugin, so no drama expected. (😉)... From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Andrew Yourtchenko Sent: Monday, November 20, 2017 1:37 PM To: Dave Barach <d...@barachs.net> Cc: vpp-dev@lists.fd.io Subject: Re: [vpp-dev] Anyone using the l2 classify path these days? Dear Dave, ACL plugin is using l2 classify path for traffic diversion and also dispatching the dot1q/dot1ad packets to the correct ip4/ip6 acl plugin node by matching on the inner ethertype... I could probably make use of this change to push some more intelligence of the stateless traffic matching to classifier as an acceleration measure for some specific cases.. (assuming the idea is to do it uniformly for input&output paths).. --a On 20 Nov 2017, at 17:58, Dave Barach <d...@barachs.net <mailto:d...@barachs.net> > wrote: Dear John, I’m wondering about copying e0->metadata into vlib_buffer (b)->l2_classify.xxx in l2_input_classify. On the face of it, that seems reasonable. Do you see obvious problems with that idea? Related question, for vpp-dev: is anyone using L2 input or output classification these days? If so, will this change help, hurt, or do nothing in your use case? Thanks... Dave _______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> https://lists.fd.io/mailman/listinfo/vpp-dev
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
