[collectd] Perl interface (was: (Generic) Java plugin available for development/testing.)

Florian Forster octo at verplant.org
Fri Feb 20 17:32:17 CET 2009

On Fri, Feb 20, 2009 at 04:03:40PM +0100, Sebastian Harl wrote:
> > This this I've implemented `plugin_dispatch_async' in ba6497bd. It
> > dispatches the values to a special `dispatch thread' in
> > src/plugin.c, so that this `read -> dispatch -> write' loop back
> > into the same plugin can be avoided. Maybe this is of use for the
> > Perl plugin, too..?
> I haven't really had any problems in that respect so far (besides that
> one deadlock a while ago, which has been solved though). Would you
> expect any other benefits from implementing that?

No, nothing really besides making it easier for plugins that register a
`read' *and* a `write' callback and have a problem with the same thread
entering `read' first and `write' second.

The issue with attaching/detaching the JVM has been solved this way in
the `Java' plugin and a potential problem with a `big interpreter lock'
in a potential Python plugin could be solved like this as well. The
reason I did not implement this in the Java plugin itself was that I
hoped other plugins (e. g. the Perl plugin) could make use of it, too.

But maybe it is simpler to implement this with `pthread_getspecific' and
friends.. I'll have a look..

Florian octo Forster
Hacker in training
GnuPG: 0x91523C3D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://mailman.verplant.org/pipermail/collectd/attachments/20090220/843b3221/attachment.pgp 

More information about the collectd mailing list