pcp
[Top] [All Lists]

Re: [pcp] PCP Updates: IPv6 for libpcp_pmda

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: [pcp] PCP Updates: IPv6 for libpcp_pmda
From: Dave Brolley <brolley@xxxxxxxxxx>
Date: Wed, 22 May 2013 10:54:03 -0400
Cc: PCP <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <1830647660.8761384.1369176112662.JavaMail.root@xxxxxxxxxx>
References: <519BB30F.3050801@xxxxxxxxxx> <1830647660.8761384.1369176112662.JavaMail.root@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4
On 05/21/2013 06:41 PM, Nathan Scott wrote:

Looking good - couple of minor nits ...

pmda.h - this is an ABI breaking change, doesn't have to be if you move the
new enum entry to the end of the set rather than in the middle.
OK. Looks like the patch you sent me incorporates this.

open.c - this too doesn't really need to risk fallout from changing the API.
Instead, I'd suggest keeping __pmdaOpenInet, add __pmdaOpenIPv6 and make 'em
one-line wrappers around your new __pmdaOpenIP (modified __pmdaOpenInet).  I
wonder if __pmdaOpenSocket might be a more natural fit as the new name here,
rather than __pmdaOpenIP?
This is not really an API change, since __pmdaOpenInet() was a static function. I have no issue with this suggestion, however, and it is consistent with the changes you made to dbpmda (also in your patch), as is the suggested name __pmdaOpenSocket(). I will make the change.

Some guidance regarding which qa test(s) to augment would be
appreciated. It's hard to tell by number :-(
110 156 199 seem like initial candidates.  Looks like they'll need the pmcd
and pmdaproc.sh support in place first though.
Thanks. I'll have a look.

Dave

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