mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Gopi Palaniappan <gpalani1@urbana.css.mot.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: memory foorprint of kernel modules
Date: Thu, 12 Feb 2004 15:45:32 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.53.0402121543070.28272@chaos> (raw)
In-Reply-To: <BDEMIINGEPCMIFLFPKCKCEFDCCAA.gpalani1@urbana.css.mot.com>

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.



  reply	other threads:[~2004-02-12 20:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-12 20:24 Gopi Palaniappan
2004-02-12 20:45 ` Richard B. Johnson [this message]
2004-02-12 22:34   ` Gopi Palaniappan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.53.0402121543070.28272@chaos \
    --to=root@chaos.analogic.com \
    --cc=gpalani1@urbana.css.mot.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®