pcp
[Top] [All Lists]

Re: [pcp] [RFC] Reducing installed PCP package sizes

To: Nathan Scott <nathans@xxxxxxxxxx>, PCP <pcp@xxxxxxxxxxx>
Subject: Re: [pcp] [RFC] Reducing installed PCP package sizes
From: Mark Goodwin <mgoodwin@xxxxxxxxxx>
Date: Wed, 17 Sep 2014 10:57:18 +1000
Cc: Jeremy Eder <jeder@xxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <236430128.44517548.1409912159545.JavaMail.zimbra@xxxxxxxxxx>
References: <236430128.44517548.1409912159545.JavaMail.zimbra@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0
On 09/05/2014 08:15 PM, Nathan Scott wrote:
[ ... ]
2. Many PMDAs (including "core" PMDAs) have both daemon & DSO
variants which duplicate a bit of code (hence increasing the
installed package size ondisk).  I wonder if we could move to
a model where the daemon PMDAs in such cases use the run-time
DSO, instead of linking with the .o at build time?  (this'll
need a new libpcp_pmda helper function to wrap the dlopen(3)
call).

That could work. Another idea could be to only ship the DSO
variant for some PMDAs, which would be preferable to shipping
only the daemon - for local context support.

We could add a new PMDA_INTERFACE version that supports e.g.
FOO_args(argc, argv) or perhaps an extended FOO_init() that has
support for args, something like that. PMDAs that need arguments
(such as the logger PMDA) could then be DSOs, which would be a
step closer to a viable pmlogger that only uses a local context
(no pmcd required for a minimal logging deployment).

Cheers
-- Mark

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