From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266579AbUBLUwI (ORCPT ); Thu, 12 Feb 2004 15:52:08 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266590AbUBLUwI (ORCPT ); Thu, 12 Feb 2004 15:52:08 -0500 Received: from chaos.analogic.com ([204.178.40.224]:15237 "EHLO chaos.analogic.com") by vger.kernel.org with ESMTP id S266579AbUBLUwD (ORCPT ); Thu, 12 Feb 2004 15:52:03 -0500 Date: Thu, 12 Feb 2004 15:45:32 -0500 (EST) From: "Richard B. Johnson" X-X-Sender: root@chaos Reply-To: root@chaos.analogic.com To: Gopi Palaniappan cc: linux-kernel@vger.kernel.org Subject: Re: memory foorprint of kernel modules In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 12 Feb 2004, Gopi Palaniappan wrote: > Is there an easy way to measure the memory/RAM footprint of dynamically > loaded kernel modules? > Are there tools similar to "pmap" for this purpose? > > thanks, > Gopi > -- > Motorola Inc. > Personal Communications Sector, > Urbana-Champaign Design Center, > 1800 S. Oak St, Champaign, IL 61820. > You might make some sense of /proc/ksyms... This is for a module called ramdisk. Script started on Thu Feb 12 15:41:10 2004 cd /proc # strings ksyms | grep ramdisk [ramdisk] [ramdisk] [ramdisk] [ramdisk] [ramdisk] [ramdisk] [ramdisk] [ramdisk] d4a19510 __insmod_ramdisk_S.bss_L4 [ramdisk] d4a19100 __insmod_ramdisk_S.rodata_L563 [ramdisk] [ramdisk] [ramdisk] d4a18000 __insmod_ramdisk_O/root/Message-Based/drivers/target/ramdisk.o_M4027E0AD_V132120 [ramdisk] [ramdisk] [ramdisk] [ramdisk] d4a18054 __insmod_ramdisk_S.text_L4237 [ramdisk] [ramdisk] [ramdisk] [ramdisk] d4a19398 __insmod_ramdisk_S.data_L5 [ramdisk] # exit exit Script done on Thu Feb 12 15:41:45 2004 Cheers, Dick Johnson Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips). Note 96.31% of all statistics are fiction.