Messages in this thread | | | Date | Thu, 14 Sep 2006 21:03:12 +0200 (added by ) | From | grundig <> | Subject | Re: [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108 |
| |
El Thu, 14 Sep 2006 08:14:19 -0700, "Martin J. Bligh" <mbligh@mbligh.org> escribió:
> 2. You can get zero overhead by CONFIG'ing things out.
IOW, no distro will enable it by default to avoid the overhead, making it useless for lots of real-world working systems where you need to guess what's hapenning to software running real workloads that can't just be stopped.
I guess there's no problem in having both LTT and Kprobes merged in the main tree at the same time. But Kprobes + systemtap will get enabled and used by distros massively just because users can start using it inmediately, without recompiling or installing extra kernels and rebooting. There're cases where distros may want to enable automatic tracing in every boot and only on boot but that don't like to suffer from an extra performance hit after booting...
I'm not meaning that LTT sucks and doesn't have advantages and that doesn't deserve being merged/used, it just looks like kprobes+systemtap will get way more real-world users no matter how much you discuss here - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |