Hi! I have a few questions in the MAP-E/MAP-T area.
First the easy one: In the src/plugin/map/map.h file, there is a #include <map/map_dpo.h>. That works fine in the source tree and the source-tree-based builds. However, once installed on a system where out-of-tree builds take place, It makes for an odd system-level include path because the "vpp_plugins" piece is missing. Can we change that to '#include <vpp_plugins/map/map_dpo.h>"? And second, are there plans somewhere already in-motion to add an API interface to the MAP-E/T configuration parameters? They are already available and configurable by the vppctl CLI, but not via the API. Would anyone be interested in a patch to refactor that parameter handling to allow API access to those parameters too? Finally, are there any known issues/bugs in the MAP-E/MAP-T packet-handling? Thanks, jdl
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11318): https://lists.fd.io/g/vpp-dev/message/11318 Mute This Topic: https://lists.fd.io/mt/28244962/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
