From owner-freebsd-current@FreeBSD.ORG Tue Jun 6 06:28:00 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9BDA16AC9F for ; Tue, 6 Jun 2006 06:20:39 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8327E43D48 for ; Tue, 6 Jun 2006 06:20:39 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 1F27E46BAF; Tue, 6 Jun 2006 02:20:39 -0400 (EDT) Date: Tue, 6 Jun 2006 07:20:39 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: bhuvan.kumarmital@wipro.com In-Reply-To: Message-ID: <20060606071736.J68996@fledge.watson.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: libmemstat(3) - Library for monitoring kernel memory use X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jun 2006 06:28:02 -0000 On Tue, 6 Jun 2006 bhuvan.kumarmital@wipro.com wrote: > Saw your tool (memtop) for monitoring kernel memory. I'd like to use a > similar tool for linux, i believe your tool is bsd based. Could you tell me > a similar tool, or perhaps another version of memtop built for linux. I'd > really appreciate you help. Please reply on my email address. Bhuvan, You are correct that libmemstat and derived tools currently rely on features present in the FreeBSD kernel. The library provides a general monitoring abstraction over a set of specific kernel memory allocators -- specifically, the FreeBSD malloc(9) and uma(9) allocators. It is relatively straight forward to implement that abstraction for other memory allocators, such as user space allocators or kernel allocators from other platforms, but that work has not been done (as far as I know). I'm not aware of specific monitoring tools for the Linux operating system that are able to perform this type of profiling/monitoring, although I presume some sort of kernel memory profiling tool does exist. Thanks, Robert N M Watson