As a matter of discipline, you’d be better off to continue binding symbols
explicitly. Otherwise, what you end up with amounts to one plugin split into
pieces.
As things stand, if someone misconfigures the set of loaded plugins it ought to
be obvious what happened. (“Where is the foo plugin?”).
Using the global symbol table creates implicit plugin load-order dependencies
which are not helpful. We currently load plugins via dlopen (... RTLD_LAZY).
Imagine what would happen if that changed to dlopen (... RTLD_NOW).
FWIW... D.
From: vpp-dev@lists.fd.io On Behalf Of Satya Murthy
Sent: Tuesday, April 14, 2020 8:14 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] exporting plugin functions/symbols to global space
Hi,
I remember seeing some questions regarding this in fdio mailing list, but not
able to find it now.
We have a plugin which has 10 functions that are needed by 3 other plugins (
which are owned by us ).
As of now, we are doing vlib_get_plugin_symbol() and getting the symbols.
But , I remember there is a way each plugin can export the functions to global
space, so that other plugins dont need to do dlsym and get it directly from
global symbol table.
Is there any framework /macros in VPP to export all or specific symbols to
global level from a plugin, so that all the other plugins can access it without
doing dlsym.
--
Thanks & Regards,
Murthy
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#16066): https://lists.fd.io/g/vpp-dev/message/16066
Mute This Topic: https://lists.fd.io/mt/73008778/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
