On Jan 24, 2008 4:02 PM, John Carter <[EMAIL PROTECTED]> wrote:
>         in a simple scripting language), translates those instructions into C 
> code, compiles this  C  code,
>         and  loads  the resulting kernel module into a running Linux kernel 
> to perform the requested system

Wow. Nothing that I'd ever want to see on a production machine,
regardless of load. I wonder if it can cleanly unload the module after
use? Actually, I wonder if module unloading is fully supported yet at
all ...

>         The language, which is described in a later section, is strictly 
> typed, declaration free,  procedu‐
>         ral,  and  inspired  by awk.  It allows source code points or events 
> in the kernel to be associated

The whole "inspired by awk" stuff is one of my big beefs with Dtrace
itself. An ugly language, with no assistance to make scripts easy to
create. On the other hand, it's an extremely low system impact probe.
I see plenty of scope for a compiled Dtrace language, and it sounds
like a missed opportunity if SystemTap implements the worst part of
Dtrace and combines it with a non-low-impact probe methodology.

-jim

Reply via email to