Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754782AbYGWAv4 (ORCPT ); Tue, 22 Jul 2008 20:51:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753116AbYGWAvq (ORCPT ); Tue, 22 Jul 2008 20:51:46 -0400 Received: from ag-out-0708.google.com ([72.14.246.248]:54647 "EHLO ag-out-0708.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753100AbYGWAvp (ORCPT ); Tue, 22 Jul 2008 20:51:45 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent:sender; b=cTDCbolI9JVRwYvY+jkTpiHjzo6YgdkAK5MZaEtqQvR3OEhPSNP9tbFyuFv5cios0J TS1Jv7+1+rsWJxiIIq8ly0P8YirGBTIhFIIYjk52woMrIm7/3vgQSPWDiwR6LwSZ/1VB jl1XaE3qdfArzRYuUjG5SvJhOusOGBOu/Ffvk= Date: Wed, 23 Jul 2008 03:50:02 +0300 From: Eduard - Gabriel Munteanu To: "Frank Ch. Eigler" Cc: penberg@cs.helsinki.fi, cl@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, rdunlap@xenotime.net, mpm@selenic.co Subject: Re: [RFC PATCH 1/4] kmemtrace: Core implementation. Message-ID: <20080723005002.GA5206@localhost> References: <1216751493-13785-1-git-send-email-eduard.munteanu@linux360.ro> <1216751493-13785-2-git-send-email-eduard.munteanu@linux360.ro> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1452 Lines: 38 On Tue, Jul 22, 2008 at 05:28:16PM -0400, Frank Ch. Eigler wrote: > > Eduard - Gabriel Munteanu writes: > > > kmemtrace provides tracing for slab allocator functions, such as kmalloc, > > kfree, kmem_cache_alloc, kmem_cache_free etc.. Collected data is then fed > > to the userspace application in order to analyse allocation hotspots, > > internal fragmentation and so on, making it possible to see how well an > > allocator performs, as well as debug and profile kernel code. > > [...] > > It may make sense to mention in addition that this version of > kmemtrace uses markers as the low-level hook mechanism, and this makes > the data generated directly accessible to other tracing tools such as > systemtap. Thank you! > > > - FChE Sounds like a good idea, but I'd like to get rid of markers and use Mathieu Desnoyers' tracepoints instead. I'm just waiting for tracepoints to get closer to inclusion in mainline/-mm. It would be great if tracepoints completely replaced markers, so SystemTap would use those instead. However, if tracepoints are not ready when kmemtrace is to be merged, I'll take your advice and mention markers and SystemTap. Thanks, Eduard -- 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/