From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762051Ab0GUCDH (ORCPT ); Tue, 20 Jul 2010 22:03:07 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.125]:62763 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1762021Ab0GUCDF (ORCPT ); Tue, 20 Jul 2010 22:03:05 -0400 X-Authority-Analysis: v=1.1 cv=kjawQlkT3vujM0lFy4b69hWxQTW3SR1XdVtFii1ut0g= c=1 sm=0 a=XL1Npt1c_1MA:10 a=Q9fys5e9bTEA:10 a=gMqfjgEr1zLu/65IO0LwxA==:17 a=uitoBhkgsvXyM4Ob2XsA:9 a=jOv8kIbmxNlffFAkDrjDS19n-s4A:4 a=PUjeQqilurYA:10 a=gMqfjgEr1zLu/65IO0LwxA==:117 X-Cloudmark-Score: 0 X-Originating-IP: 74.67.89.75 Subject: Re: [PATCH] tracing: reduce latency and remove percpu trace_seq From: Steven Rostedt To: Lai Jiangshan Cc: Theodore Tso , Theodore Tso , linux-kernel@vger.kernel.org, Ingo Molnar , Frederic Weisbecker In-Reply-To: <4C0CA4BE.9000703@cn.fujitsu.com> References: <4C078350.7090106@cn.fujitsu.com> <1275572170.15884.30.camel@gandalf.stny.rr.com> <4C0863BD.6000307@cn.fujitsu.com> <1275620590.15884.70.camel@gandalf.stny.rr.com> <4C0CA4BE.9000703@cn.fujitsu.com> Content-Type: text/plain; charset="ISO-8859-15" Date: Tue, 20 Jul 2010 22:03:01 -0400 Message-ID: <1279677781.4818.23.camel@gandalf.stny.rr.com> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2010-06-07 at 15:50 +0800, Lai Jiangshan wrote: > Steven Rostedt wrote: > > On Fri, 2010-06-04 at 10:23 +0800, Lai Jiangshan wrote: > >> Steven Rostedt wrote: > >> > >>> The "print" in the trace_seq_printf() is the TP_printk() field of the > >>> TRACE_EVENT. I believe that there were some events (ext4?) that did > >>> things that required preemption disabled. > >>> > >> It seems that ext4 has no such events. > >> I find jbd2_dev_to_name() in the TP_printk() field of ext4's tracepoints. > >> And it seems that jbd2_dev_to_name() requires preemption enabled and sleepable. > >> > >> Maybe there were some events did things that required preemption disabled. > >> But No document ensure TP_printk() preemption disabled, such events should > >> be fixed, I think. > > > > Well, I had a private email conversation with Ted last year where IIRC, > > adding the preempt disable would fix things. > > > > I'd like to make sure Ted is OK with removing that before we do so. > > > > Ted? > > > > Hi, Ted > > Could you give some comments? > I'm waiting and will appreciate your help. Since I've not heard anything, I'm pulling this in for 2.6.36. -- Steve