From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753890AbYI0RiZ (ORCPT ); Sat, 27 Sep 2008 13:38:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752735AbYI0RiS (ORCPT ); Sat, 27 Sep 2008 13:38:18 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.123]:52021 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752687AbYI0RiR (ORCPT ); Sat, 27 Sep 2008 13:38:17 -0400 Date: Sat, 27 Sep 2008 13:38:15 -0400 (EDT) From: Steven Rostedt X-X-Sender: rostedt@gandalf.stny.rr.com To: Ingo Molnar 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 In-Reply-To: <20080927171640.GA1990@elte.hu> Message-ID: References: <20080925195522.GA22248@elte.hu> <20080925201211.GA1878@elte.hu> <20080925211017.GA12689@elte.hu> <20080925214134.GA23025@elte.hu> <20080925221441.GA29060@elte.hu> <20080927171640.GA1990@elte.hu> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. So yes, the tracer can implement anything it wants on top of the ring buffer ;-) -- Steve