Date: Wed, 1 Apr 2009 14:21:22 +0200
From: Ingo Molnar <mingo@elte.hu>
To: Tom Zanussi <tzanussi@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
       Steven Rostedt <rostedt@goodmis.org>, fweisbec@gmail.com
Subject: Re: [PATCH v2] tracing/filters: add run-time field descriptions to
	TRACE_EVENT_FORMAT events
Message-ID: <20090401122122.GF12966@elte.hu>
References: <1238478529.6749.12.camel@bookworm>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1238478529.6749.12.camel@bookworm>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 928
Lines: 21


* Tom Zanussi <tzanussi@gmail.com> wrote:

> The other is that for the really high-volume tracers e.g. the 
> function tracer, the volume of filtered events can be so high that 
> it pushes the unfiltered events out of the ring buffer before they 
> can be read so e.g. cat'ing the trace file repeatedly shows either 
> no output, or once in awhile some output but that isn't there the 
> next time you read the trace, which isn't what you normally expect 
> when reading the trace file. If you read from the trace_pipe file 
> though, you can catch them before they disappear.

yeah - this artifact of the ringbuffer needs to be fixed too. Steve, 
what's the plans on that?

	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/