From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755273AbYIWSE3 (ORCPT ); Tue, 23 Sep 2008 14:04:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753191AbYIWSES (ORCPT ); Tue, 23 Sep 2008 14:04:18 -0400 Received: from fgwmail5.fujitsu.co.jp ([192.51.44.35]:55062 "EHLO fgwmail5.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753081AbYIWSER (ORCPT ); Tue, 23 Sep 2008 14:04:17 -0400 Date: Wed, 24 Sep 2008 02:59:37 +0900 (JST) From: KOSAKI Motohiro To: Masami Hiramatsu Subject: Re: Unified tracing buffer Cc: kosaki.motohiro@jp.fujitsu.com, Martin Bligh , Linux Kernel Mailing List , Linus Torvalds , Thomas Gleixner , Mathieu Desnoyers , Steven Rostedt , od@novell.com, "Frank Ch. Eigler" , systemtap-ml In-Reply-To: <48D90970.3060409@redhat.com> References: <20080923232239.DC1E.KOSAKI.MOTOHIRO@jp.fujitsu.com> <48D90970.3060409@redhat.com> Message-Id: <20080924025457.DC24.KOSAKI.MOTOHIRO@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.42 [ja] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > I can't imazine a merit of the single-channel mode. > > Could you please explain it? > > Actually, single-channel mode is for not-frequently event tracing. > At least systemtap case, sometimes we just want to collect data > and watch it periodically(as like as 'top'). Or, just monitoring > errors as additional printk. in these cases, overhead is not so > important. > > I think the main reason of using single-channel mode is simplicity of > userspace reader. We can use 'cat' or 'tail' to read the buffer on-line. > I'm not sure how much overhead ftrace-like buffer merging routine has, > but if kernel provides an interface which gives us single-merged buffer > image(like ftrace buffer), we are grad to use it. :-) Yup, I also think it is better. Thanks.