From: "Gopi Palaniappan" <gpalani1@urbana.css.mot.com>
To: <root@chaos.analogic.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: memory foorprint of kernel modules
Date: Thu, 12 Feb 2004 16:34:25 -0600 [thread overview]
Message-ID: <BDEMIINGEPCMIFLFPKCKIEFFCCAA.gpalani1@urbana.css.mot.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0402121543070.28272@chaos>
Hi Richard:
I am not sure looking at the ksyms will give me an actual measure.
Lets take an example,
I have a driver "foo.o" that i insmod, lets say. If this driver uses kmalloc
or malloc to dynamically
utilize RAM space for its internal operation, I don't think your suggested
method will capture
that dynamic allocation of memory, am i correct?
I want to get a real-time ram usage of a specified dynamically loaded
module.
thanks,
Gopi
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?
>
>
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]
d4a19510 __insmod_ramdisk_S.bss_L4
[ramdisk]
d4a19100 __insmod_ramdisk_S.rodata_L563
d4a18000
__insmod_ramdisk_O/root/Message-Based/drivers/target/ramdisk.o_M4027E0AD_V13
2120
d4a18054 __insmod_ramdisk_S.text_L4237
d4a19398 __insmod_ramdisk_S.data_L5
[ramdisk]
# exit
prev parent reply other threads:[~2004-02-12 22:34 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
2004-02-12 22:34 ` Gopi Palaniappan [this message]
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=BDEMIINGEPCMIFLFPKCKIEFFCCAA.gpalani1@urbana.css.mot.com \
--to=gpalani1@urbana.css.mot.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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®