This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Integrate delay accounting with systemtap?

From: fche at redhat dot com (Frank Ch. Eigler)
To: ananth at in dot ibm dot com
Cc: Mike Mason <mmlnx at us dot ibm dot com>, SystemTAP <systemtap at sources dot redhat dot com>
Date: 12 Jul 2007 10:13:16 -0400
Subject: Re: Integrate delay accounting with systemtap?
References: <20070711060617.GA16126@in.ibm.com> <46951B6D.60107@us.ibm.com> <20070712042109.GB9636@in.ibm.com>

Ananth N Mavinakayanahalli <ananth@in.ibm.com> writes:

> [...]  We shouldn't be using any probes or functions in kernel for
> this feature. Rather, SystemTap should be taught to listen to the
> netlink socket where this information is available.

What do you mean by "listen to the netlink socket"?  The netlink
widget is (roughly speaking) a way for user-space programs to run
kernel queries outside the many other available methods.  But
systemtap scripts already run in kernel space.  How/why would you want
them to talk across netlink sockets?

- FChE

Follow-Ups:
- Re: Integrate delay accounting with systemtap?
  - From: Ananth N Mavinakayanahalli

References:
- Integrate delay accounting with systemtap?
  - From: Ananth N Mavinakayanahalli
- Re: Integrate delay accounting with systemtap?
  - From: Mike Mason
- Re: Integrate delay accounting with systemtap?
  - From: Ananth N Mavinakayanahalli

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]