> -----Original Message----- > From: stephane eranian [mailto:[EMAIL PROTECTED] > Sent: Monday, September 08, 2008 4:34 PM > To: Dan Terpstra > Cc: perfmon2-devel > Subject: Re: [perfmon2] pfm_delete_evtsets() going away in v3 > > Dan, > > On Wed, Sep 3, 2008 at 5:19 PM, Dan Terpstra <[EMAIL PROTECTED]> > wrote: > > Depends on what you mean by 'heavily'. PAPI calls it in two places: once > in > > the PAPI_stop functionality, to basically clean things up; and once in a > > routine that checks multiplexing behavior and creates a scratch event > set > > for testing. Seems that for long-running applications where calipers may > > come and go, event sets should be considered as ephemeral. 'delete' > seems > > naturally symmetric to 'create'. > > - d > > > I meant that without it, you have a lot of code restructuring to do or > the logic of > you application will have to change. > > Yes, I agree about the need for symmetry without going to close(). But > if the call > is seldom used, then it means it is superfluous and we can live > without it for now. > I think the case for pfm_delete_evtsets() is weaker than the need for > load/unload > of the context. Would you agree with that? > Reluctantly. I can appreciate the desire for a streamlined UI, especially in the face of the kernel gatekeepers. And PAPI has a tradition of adapting to whatever infrastructure is provided by the underlying tools. I just feel better about being able to clean up behind myself. I can envision use cases where large numbers of event sets could be created and stranded, but realistically these are most likely edge cases. - d > > > >> -----Original Message----- > >> From: [EMAIL PROTECTED] [mailto:perfmon2- > devel- > >> [EMAIL PROTECTED] On Behalf Of stephane eranian > >> Sent: Wednesday, September 03, 2008 10:42 AM > >> To: perfmon2-devel > >> Subject: [perfmon2] pfm_delete_evtsets() going away in v3 > >> > >> Hello, > >> > >> I am in the process of redesigning the perfmon API for the v3 version > >> so it is more > >> acceptable to the LKML people. I know it is painful, but hopefully it > >> will succeed. > >> > >> I am thinking of dropping pfm_delete_evtsets(). That means you could > not > >> delete > >> an event set. You would have to destroy the context and start over. > >> > >> if you are heavily relying on this call, please make yourself heard > ASAP. > >> > >> Thanks. > >>
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ perfmon2-devel mailing list perfmon2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
