Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758194AbZIQRgJ (ORCPT ); Thu, 17 Sep 2009 13:36:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754840AbZIQRgI (ORCPT ); Thu, 17 Sep 2009 13:36:08 -0400 Received: from casper.infradead.org ([85.118.1.10]:58024 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754774AbZIQRgH (ORCPT ); Thu, 17 Sep 2009 13:36:07 -0400 Date: Thu, 17 Sep 2009 19:35:43 +0200 From: Arjan van de Ven To: Linus Torvalds Cc: Jamie Lokier , Evgeniy Polyakov , Eric Paris , David Miller , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, netdev@vger.kernel.org, viro@zeniv.linux.org.uk, alan@linux.intel.com, hch@infradead.org Subject: Re: fanotify as syscalls Message-ID: <20090917193543.5f88e2b1@infradead.org> In-Reply-To: References: <1252703626.2305.50.camel@dhcp231-106.rdu.redhat.com> <20090911212731.GA19901@shareable.org> <1252705902.2305.83.camel@dhcp231-106.rdu.redhat.com> <20090912094110.GB24709@ioremap.net> <20090914001759.GB30621@shareable.org> <20090914140720.GA8564@ioremap.net> <1252955295.2246.35.camel@dhcp231-106.rdu.redhat.com> <20090915201620.GB32192@ioremap.net> <1253051699.5213.18.camel@dhcp231-106.rdu.redhat.com> <20090916120523.GA12830@ioremap.net> <20090916122723.GE29359@shareable.org> Organization: Intel X-Mailer: Claws Mail 3.7.2 (GTK+ 2.14.7; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by casper.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1146 Lines: 31 On Thu, 17 Sep 2009 09:40:16 -0700 (PDT) Linus Torvalds wrote: > > And then we have page faults. I've long wished that from a system > call tracing standpoint we could show page faults as > pseudo-system-calls (at least as long as they happen from user space > - trying to handle nesting is not worth it). It would make it _so_ > much more obvious what the performance patterns are if you could just > do > > strace -ttT firefox > > for the cold-cache case and you'd see where the time is really spent. > > (yeah, yeah, you can get that kind of information other ways, but > it's a hell of a lot less convenient than just getting a nice trace > with timestamps). ohhh I should add pagefaults to timechart good one. -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org -- 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/