This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
RE: Tapset state & plans
- From: "Nguyen, Thang P" <thang dot p dot nguyen at intel dot com>
- To: "Mike Mason" <mmlnx at us dot ibm dot com>, <systemtap at sources dot redhat dot com>
- Date: Sun, 24 Sep 2006 14:55:37 -0700
- Subject: RE: Tapset state & plans
-----Original Message-----
From: systemtap-owner@sourceware.org
[mailto:systemtap-owner@sourceware.org]
> Mike Mason wrote:
>> I've been asked to do is help expand and enhance systemtap's set of
>> tapsets. As a starting point, I have some questions regarding the
>> current state of things:
>>
>> - What analysis has been done to determine what tapsets should be
>> implemented? Has anyone done a comparison between the data that
dtrace
>> provides and what systemtap does/should provide?
>>
>> - Of the tapsets already in cvs, which are considered complete and
>> which are incomplete. I know things like this are never truly "done",
>> but some must be more done than others.
>>
>> - What tapsets are people in the community currently working on?
>>
>> - Does a prioritized list of tapsets "to be done" exist?
>>
>> Thanks,
>> Mike Mason
>>
The block I/O and tcp/upd tapsets should be completed. These tapsets
should contain important probe points, and they certainly can be
improved further. I am not aware if we have a prioritized list of
tapsets, or if any analysis (dtrace comparison) is currently available.
Thang