dtrace clone

Posted Aug 10, 2007 14:48 UTC (Fri) by fuhchee (guest, #40059)
In reply to: DTrace real port by man_ls
Parent article: On DTrace envy

There are several obstacles. Rewriting the code is a relatively small part. Merging upstream is huge and controversial. There may also be legal (patent) barriers.

dtrace clone

Posted Aug 10, 2007 23:09 UTC (Fri) by man_ls (guest, #15091) [Link] (3 responses)

Merging upstream has to be done with SystemTap too. Is there any reason why it would be harder with a dtrace clone?

And patent trouble has not stopped kernel developers before...

dtrace clone

Posted Aug 11, 2007 20:53 UTC (Sat) by fuhchee (guest, #40059) [Link]

> Merging upstream has to be done with SystemTap too.

Not as much as one might think. Systemtap relies only on existing
externalized kernel interfaces and hooks - no changes just on our
account. That's not to say it wouldn't be nice to get some extra
interfaces/hooks, or to offload some version drift maintenance to other
folks. It means that we can work toward their development and upstream
inclusion gradually, without blocking the rest of the work.

dtrace clone

Posted Aug 11, 2007 22:09 UTC (Sat) by dlang (guest, #313) [Link] (1 responses)

please name anything in the kernel that has been put in if there is any doubt about the legality of it.

the license and patent status of dtrace is very much a reason for it not being considered (in fact, due to these issues most of the kernel developers don't even look at it to avoid any accusations of them being tainted)

dtrace clone

Posted Aug 12, 2007 12:13 UTC (Sun) by man_ls (guest, #15091) [Link]

As you probably know, any non-trivial piece of code probably infringes on a lot of patents. That hasn't stopped kernel developers from improving the kernel, and rightly so. Maybe the situation with specific patents is different.