1PMAPI_INTERNAL(3) Library Functions Manual PMAPI_INTERNAL(3)
2
3
4
6 PMAPI_INTERNAL - internal details for the Performance Metrics Applica‐
7 tion Programming Interface
8
10 #include "pmapi.h"
11 #include "libpcp.h"
12
13 ... assorted routines ...
14
15 cc ... -lpcp
16
18 This documentation is intended for internal Performance Co-Pilot (PCP)
19 developer use.
20
21 These interfaces are not part of the PCP APIs that are guaranteed to
22 remain fixed across releases, and they may not work, or may provide
23 different semantics at some point in the future.
24
26 Refer to PMAPI(3) for general information about the external interfaces
27 defined in <pcp/pmapi.h>. The interfaces described here assume that
28 context.
29
31 The following groups of internal functions and services in libpcp are
32 restricted to being called from a single-thread, and this is enforced
33 by returning PM_ERR_THREAD when an attempt to call the routines in each
34 group from more than one thread is detected.
35
36 1. The interval timer services use global state with semantics that
37 demand it is only used in the context of a single thread, so
38 __pmAFregister(3), __pmAFunregister(3), __pmAFblock(3), __pmAFun‐
39 block(3) and __pmAFisempty(3).
40
41 2. The following access control manipulation routines that are princi‐
42 pally intended for single-threaded applications: __pmAccAddOp,
43 __pmAccSaveHosts, __pmAccRestoreHosts, __pmAccFreeSavedHosts,
44 __pmAccAddHost, __pmAccAddClient, __pmAccDelClient and __pmAcc‐
45 DumpHosts.
46
47 3. The following routines that identify pmlogger control ports and are
48 principally intended for single-threaded applications: __pmLogFind‐
49 Port and __pmLogFindLocalPorts.
50
52 PMAPI(3).
53
54
55
56Performance Co-Pilot PCP PMAPI_INTERNAL(3)