Hi, Hidden visibility looks like a reasonable next step for libvnet.
For out-of-tree plugins, this is not fundamentally different from the API changes VPP already makes from one release to another: plugins need to be rebuilt and validated against their target VPP version, and any missing exports can be reviewed and added at that point. It would also give libvnet a more explicit interface and make its visibility model consistent with vppinfra and the VPP plugins, which already use hidden visibility with explicit exports. Unless anyone objects, I can prepare an RFC patch enabling hidden visibility, exporting the current in-tree requirements, fixing the weak trace hook, and adding dynamic-symbol and plugin-loading checks. We can then benchmark the actual implementation on ARM64. Internal binding of exported functions can remain a separate performance change. Best, Jerome
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#27146): https://lists.fd.io/g/vpp-dev/message/27146 Mute This Topic: https://lists.fd.io/mt/120410674/21656 Group Owner: [email protected] Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/14379924/21656/631435203/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
