pcp
[Top] [All Lists]

Re: Multi-Volume Archive + Live Data Playback for PCP Client Tools

To: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Subject: Re: Multi-Volume Archive + Live Data Playback for PCP Client Tools
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Wed, 05 Nov 2014 06:49:48 +1100
Cc: 'Dave Brolley' <brolley@xxxxxxxxxx>, 'PCP Mailing List' <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <20141104021814.GD3859@xxxxxxxxxx>
References: <542C21AE.1010504@xxxxxxxxxx> <007e01cfe010$7867f090$6937d1b0$@internode.on.net> <545110DC.2020104@xxxxxxxxxx> <y0mtx2hmwml.fsf@xxxxxxxx> <001d01cff6d7$0e9e4a50$2bdadef0$@internode.on.net> <20141103142643.GA3859@xxxxxxxxxx> <5457F82D.3050307@xxxxxxxxxxxxxxxx> <20141103215816.GC3859@xxxxxxxxxx> <54580B6A.1090007@xxxxxxxxxxxxxxxx> <20141104021814.GD3859@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
On 04/11/14 13:18, Frank Ch. Eigler wrote:
Hi, Ken -

[...]  I was not advocating a fixed mapping [...]

Aha.

The pmdaCache* routines would allow a dense allocation of more than 4
million unique ids and maintain a persistent mapping from the PMNS name
that the PMDA chooses and those unique ids.

OK, that could work.

Attached is a quick script that uses the pmns data Frank sent me and the qa test program pmdacache to demonstrate how a persistent name <--> id map could be managed by the papi PMDA.

Attachment: papi_pmns_demo
Description: Text document

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