Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965129AbWIQVsI (ORCPT ); Sun, 17 Sep 2006 17:48:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965130AbWIQVsI (ORCPT ); Sun, 17 Sep 2006 17:48:08 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:38810 "EHLO mx2.mail.elte.hu") by vger.kernel.org with ESMTP id S965129AbWIQVsE (ORCPT ); Sun, 17 Sep 2006 17:48:04 -0400 Date: Sun, 17 Sep 2006 23:40:00 +0200 From: Ingo Molnar To: Roman Zippel Cc: Nick Piggin , Thomas Gleixner , karim@opersys.com, Andrew Morton , Paul Mundt , Jes Sorensen , Mathieu Desnoyers , linux-kernel@vger.kernel.org, Christoph Hellwig , Ingo Molnar , Greg Kroah-Hartman , Tom Zanussi , ltt-dev@shafik.org, Michel Dagenais Subject: Re: [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108 Message-ID: <20060917214000.GD2145@elte.hu> References: <20060916230031.GB20180@elte.hu> <20060917084207.GA8738@elte.hu> <20060917152527.GC20225@elte.hu> <450D7EF0.3020805@yahoo.com.au> <450D8C58.5000506@yahoo.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-ELTE-SpamScore: -2.9 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.9 required=5.9 tests=ALL_TRUSTED,AWL,BAYES_50 autolearn=no SpamAssassin version=3.0.3 -3.3 ALL_TRUSTED Did not pass through any untrusted hosts 0.5 BAYES_50 BODY: Bayesian spam probability is 40 to 60% [score: 0.5000] -0.1 AWL AWL: From: address is in the auto white-list X-ELTE-VirusStatus: clean Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1467 Lines: 32 * Roman Zippel wrote: > > As an aside, there are quite a number of different types of tracing > > things (mostly static, compile out) in the kernel. Everything from > > blktrace to various userspace notifiers to lots of /proc/stuff could > > be considered a type of static event tracing. I don't know what my > > point is other than all these big, disjoint frameworks trying to be > > pushed into the kernel. Are there any plans for working some things > > together, or is that somebody else's problem? > > All the controversy around static tracing in general and LTT in > specific has prevented this so far... BLKTRACE is a special-purpose tracing facility limited to one subsystem and written and maintained by the /same/ person (Jens) who maintains that subsystem. He maintains the subsystem, the tracer and the userspace tool that extracts the tracer data. LTT on the other hand is a static tracer that affects _all_ subsystems. That is a very different situation from a maintainance overhead POV, and i believe you must know that. your suggestion that this controversy has prevented consolidation in this area is baseless and misleading, please correct or retract it. Ingo - 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/