You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any reason that an ldms sampler plugin could not simply use ldmsd_msg_logger() directly instead of using the function pointer that is passed to the sampler through get_plugin()?
Using the exported symbol directly is much preferable to a plugin implementer when they are using multiple files in their plugin for organizational purposes. Using the function pointer, combined with the ldmsd rule that all globals must be file-scope in samplers results in unnecessary cruft in the code.
The text was updated successfully, but these errors were encountered:
I proposed an ovis logging library (olog) in ldms v2 (and the code is still in the tree) so that main and plugins would have equal access to the logging symbols via a library. It was rejected at the time. The log functions are in the file with main, which isn't highly portable, so we pass them by pointer currently.
Is there any reason that an ldms sampler plugin could not simply use ldmsd_msg_logger() directly instead of using the function pointer that is passed to the sampler through get_plugin()?
Using the exported symbol directly is much preferable to a plugin implementer when they are using multiple files in their plugin for organizational purposes. Using the function pointer, combined with the ldmsd rule that all globals must be file-scope in samplers results in unnecessary cruft in the code.
The text was updated successfully, but these errors were encountered: