From: Chris Friesen <cfriesen@nortel.com>
To: "Artem B. Bityuckiy" <dedekind@oktetlabs.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: any way to find out kernel memory usage?
Date: Wed, 27 Apr 2005 10:57:16 -0600 [thread overview]
Message-ID: <426FC46C.4070306@nortel.com> (raw)
In-Reply-To: <426FC0FE.2090900@oktetlabs.ru>
Artem B. Bityuckiy wrote:
> Chris Friesen wrote:
>> Is
>> there any way to find out how much memory the kernel is using? I
>> don't see anything in /proc, but maybe something internal that isn't
>> currently exported?
>>
> How about /proc/slabinfo ?
Hmm...if I'm reading that correctly, I should be able to get the total
kernel memory usage by summing up
num_slabs*pagesperslab
for all listed slabs. Does that sound right?
I assume kmalloc/vmalloc use the "size-x" slabs?
Chris
next prev parent reply other threads:[~2005-04-27 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 16:38 any way to find out kernel memory usage? Chris Friesen
2005-04-27 16:42 ` Artem B. Bityuckiy
2005-04-27 16:57 ` Chris Friesen [this message]
2005-04-27 17:20 ` Robert Love
2005-04-27 17:44 ` Chris Friesen
2005-04-27 17:47 ` Robert Love
2005-04-27 22:23 ` Mark Lord
2005-04-27 18:07 ` Coywolf Qi Hunt
2005-04-27 18:29 ` Richard B. Johnson
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=426FC46C.4070306@nortel.com \
--to=cfriesen@nortel.com \
--cc=dedekind@oktetlabs.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.