3 ms·
Congrats, this is good news. > On Linux, some out-of-tree tracers like SystemTap could serve these needs, but brought their own challenges. I was pretty happy
by wyldfire 10y ago
Congrats, this is good news.
> On Linux, some out-of-tree tracers like SystemTap could serve these needs, but brought their own challenges.
I was pretty happy with stap, it had a really rich feature set.
> DTrace has its own concise language, D, similar to awk, whereas bcc uses existing languages (C and Python or lua) with libraries.
I think we need more creative names for languages. The short and simple ones like "go" and "D" keep on having collisions. :)
>BPF adds ... uprobes
uprobes + all the other stuff is really killer, I like the idea of watching for stuff like "my app has crossed this threshold and then this system condition occurs". At least when I tried it a couple years ago with stap my kernel wasn't built with uprobes support and I wasn't inclined to rebuild it. Hopefully it becomes (or has become) more mainstream.
- brendangregg 10y ago> I was pretty happy with stap, it had a really rich feature set. So are other companies. I mentioned it in the post, as in a way this hurt BPF development, as companies that normally would have contributed resources said they were satisfied with stap. Exciting times might be ahead for stap, if it continues its BPF backend. As for naming, yes, we need better names. Maybe the bcc/Python/BPF combination can be named something?