Q: As the father of DTrace, how do you think the prospect of the DTrace? Do you have any new feature plan for DTrace? What do you think of Oracle's porting DTrace on Linux? A: I think the prospects of DTrace are pretty good -- I certainly still use it every day. 😉 The most important immediate direction for DTrace is its (true) arrival in Linux via Triton -- and making sure that esoteric features like USDT providers and (more challengingly) ustack helpers can work on Linux binaries. (We've done the former; we're working on the latter.) In term's of Oracle and DTrace: it remains true that Oracle's port is the most complete -- and it's also the only one that is (or indeed, can be) closed source. That Oracle has left their port proprietary is classic Oracle: willful disregard for the social contracts of open source, or for the legacy of Sun. (And indeed, had they not bought Sun, this act would violate the license of DTrace.) Leave it to Oracle to pioneer new shades of mendacious behavior!
Q: There are some useful DTrace user guides, but it seems there lacks a detailed or drill-down analysis of DTrace source code. Do you have any plans to write some articles or books about DTrace source code? I think it maybe help more people to know DTrace. A: For the source code itself, I would put it up against anything for the thoroughness of its commenting; once you understand the DTrace guide, go here: https://github.com/illumos/illumos-gate/blob/master/usr/src/uts/common/sys/dtrace_impl.h, https://github.com/illumos/illumos-gate/blob/master/usr/src/uts/common/dtrace/dtrace.c. If that's too low-level but you're looking for something beyond (or in addition to) the documentation, see out 2004 USENIX paper (https://www.usenix.org/legacy/event/usenix04/tech/general/full_papers/cantrill/cantrill.pdf) and my 2006 ACM article(http://queue.acm.org/detail.cfm?id=1117401). And then of course, there are Brendan Gregg's books: DTrace and Systems Performance. Point is: there's plenty of information out there -- you just need to read it.