Hi Dave, By "e0->metadata", do you mean the u16 metadata field from the vnet_classify_entry_t struct and you would like to copy it to a field in vnet buffer l2_classify struct? If storage and consumption of metadata are in the same feature node, I do not see obvious problems as I am guessing usages of the l2_classify fields by other VPP features would not be in conflict.
I am not aware of usage of l2-input-classify or l2-output-classify features by users with whom I have been involved. Regards, John From: Dave Barach [mailto:d...@barachs.net] Sent: Monday, November 20, 2017 11:58 AM To: John Lo (loj) <l...@cisco.com> Cc: vpp-dev@lists.fd.io Subject: Anyone using the l2 classify path these days? 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 https://lists.fd.io/mailman/listinfo/vpp-dev
