[DTrace-devel] [PATCH V2 1/1 (was 0/1 by accident)] tools/dtrace: initial implementation of DTrace

[Jonathan Corbet]

On Wed, 10 Jul 2019 21:32:25 +0200
Daniel Borkmann <daniel at iogearbox.net> wrote:

> Looks like you missed Brendan Gregg's prior feedback from v1 [0]. I haven't
> seen a strong compelling argument for why this needs to reside in the kernel
> tree given we also have all the other tracing tools and many of which also
> rely on BPF such as bcc, bpftrace, ply, systemtap, sysdig, lttng to just name
> a few.

So I'm just watching from the sidelines here, but I do feel the need to
point out that Kris appears to be trying to follow the previous feedback
he got from Alexei, where creating tools/dtrace is exactly what he was
told to do:

  https://urldefense.proofpoint.com/v2/url?u=https-3A__lwn.net_ml_netdev_20190521175617.ipry6ue7o24a2e6n-40ast-2Dmbp.dhcp.thefacebook.com_&d=DwIDAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=TH500uwHRHLHqjhgluCyxMsbZEewvpf7ynuq0G-WrEk&m=nfIzLl36XfzUDFFM802KBQhhwh33nQjHuMS_ZQWE3hM&s=Ukw4knO0deTdli0wTNq8Hd6WJbs8PsCm5u9Tv8ddazU&e= 

Now he's being told the exact opposite.  Not the best experience for
somebody who is trying to make the kernel better.

There are still people interested in DTrace out there.  How would you
recommend that Kris proceed at this point?

Thanks,

jon