pcp
[Top] [All Lists]

Re: Async events

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: Async events
From: fche@xxxxxxxxxx (Frank Ch. Eigler)
Date: Mon, 14 Jul 2014 07:33:07 -0400
Cc: Dave Brolley <brolley@xxxxxxxxxx>, pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <1811055467.9278554.1405310559100.JavaMail.zimbra@xxxxxxxxxx> (Nathan Scott's message of "Mon, 14 Jul 2014 00:02:39 -0400 (EDT)")
References: <20140619194444.3B03D58015@xxxxxxxx> <y0mpphe60bw.fsf@xxxxxxxx> <53BD8921.3000306@xxxxxxxxxx> <2109477330.6980142.1404945968324.JavaMail.zimbra@xxxxxxxxxx> <53BE9F30.7010106@xxxxxxxxxx> <1543911711.7865026.1405028479709.JavaMail.zimbra@xxxxxxxxxx> <53C03CCF.3000908@xxxxxxxxxx> <167962287.9276874.1405309225214.JavaMail.zimbra@xxxxxxxxxx> <1811055467.9278554.1405310559100.JavaMail.zimbra@xxxxxxxxxx>
User-agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux)
nathans wrote:

> Oh forgot to mention this...
> [...]
> See src/libpcp/src/AF.c btw - provides one, cross-platform model you might
> consider for:

At least two latent problems should give one pause:
- use of SIGALRM and queue structures in a thread-unsafe manner
- use of numerous async-signal-unsafe functions in onalarm() signal
  handler, and callback functions listed __pmAFregister

> (pmlogger uses that stuff extensively, for example)

To some extent, it's been lucky!

One more thing.  The functions in AF.c are all __-prefixed,
dso-exported, declared only in impl.h, and in this case used by a
client.  I have several times asked what __ prefixing is supposed to
mean, when we use it so arbitrarily.  This is a case in point.

- FChE

<Prev in Thread] Current Thread [Next in Thread>