Messages in this thread | | | From | Kyle Moffett <> | Date | Sat, 6 Aug 2011 19:14:13 -0400 | Subject | Re: [RFC][PATCH 0/8] Having perf use libparsevent.a |
| |
On Sat, Aug 6, 2011 at 17:40, Steven Rostedt <rostedt@goodmis.org> wrote: > On Sat, 2011-08-06 at 14:47 -0400, Kyle Moffett wrote: >> On Aug 6, 2011 11:35 AM, "Steven Rostedt" <rostedt@goodmis.org> wrote: >>> On Sat, 2011-08-06 at 09:16 -0600, David Ahern wrote: >>>> If the library is just for parsing trace events why not call it >>>> libtraceparse or libtrace? This isn't perf specific functionality. >>> >>> Actually, I'm thinking libevents would probably be most appropriate. >>> It has less to do with perf in general, and more about events. Even >>> reading the events goes under this category. >> >> Ooh, please don't... "libevent" is already an epoll() event-based >> application helper library and this would be overly confusing. > > OK, what about libkevent, as this has to do with kernel events.
Hmm, well "kevent()" is a BSD syscall that does the same kinds of things as "epoll()" does on Linux. It's used by libevent, in fact.
Maybe "libkernevent"? A quick google doesn't find anything problematic there... Other options with minimal chance of confusion are: libkernelevent liblinuxevent libinuxevent (Linked with option "-linuxevent")
To be honest I don't really see anything wrong with a name involving "trace"... Perhaps something like libevtrace/libtraceevent/etc?
Cheers, Kyle Moffett
| |