From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753685AbYI0StY (ORCPT ); Sat, 27 Sep 2008 14:49:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754518AbYI0StD (ORCPT ); Sat, 27 Sep 2008 14:49:03 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:60299 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754273AbYI0StB (ORCPT ); Sat, 27 Sep 2008 14:49:01 -0400 Date: Sat, 27 Sep 2008 20:42:12 +0200 From: Ingo Molnar To: Steven Rostedt Cc: Linus Torvalds , Martin Bligh , Peter Zijlstra , Martin Bligh , linux-kernel@vger.kernel.org, Thomas Gleixner , Andrew Morton , prasad@linux.vnet.ibm.com, Mathieu Desnoyers , "Frank Ch. Eigler" , David Wilder , hch@lst.de, Tom Zanussi , Steven Rostedt Subject: Re: [RFC PATCH 1/3] Unified trace buffer Message-ID: <20080927184212.GB13685@elte.hu> References: <20080925201211.GA1878@elte.hu> <20080925211017.GA12689@elte.hu> <20080925214134.GA23025@elte.hu> <20080925221441.GA29060@elte.hu> <20080927171640.GA1990@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Steven Rostedt wrote: > > On Sat, 27 Sep 2008, Ingo Molnar wrote: > > > > If all you do is to trace high-freq events on all CPUs and you are _not_ > > interested in the precise interactions, the overhead of global > > synchronization can hurt a lot. > > > > In any case, SMP coherency of trace events is an independent property of > > the tracer, and preferably something that can be turned on/off. > > Just a note. The current ring buffering system that I'm proposing > keeps its own time stamp counter (currently sched_clock) that will > most likely be updated later. I'm trying to keep this ring buffer > system as dumb as possible. It does not even implement the merge sort. > That's up to the tracer to handle. There's nothing stopping the trace > from adding some atomic counter to each event to help it sort. correct. The price is all the notifier/callback overhead and the loss of type checking of the record contents. But that's an unavoidable price of abstraction, at least in C. > So yes, the tracer can implement anything it wants on top of the ring > buffer ;-) yes, very nice! :) Ingo