From: Chris Friesen <cfriesen@nortel.com>
To: Robert Love <rml@novell.com>
Cc: "Artem B. Bityuckiy" <dedekind@oktetlabs.ru>,
linux-kernel@vger.kernel.org
Subject: Re: any way to find out kernel memory usage?
Date: Wed, 27 Apr 2005 11:44:27 -0600 [thread overview]
Message-ID: <426FCF7B.5020806@nortel.com> (raw)
In-Reply-To: <1114622438.10836.8.camel@betsy>
Robert Love wrote:
> On Wed, 2005-04-27 at 10:57 -0600, Chris Friesen wrote:
>
>
>>I assume kmalloc/vmalloc use the "size-x" slabs?
>
>
> kmalloc, yes.
>
> vmalloc is separate, totally unrelated, space.
>
> Statistics are in /proc/meminfo.
Okay, so can I get the total amount of memory used by the kernel based
on meminfo output? (Slab + VmallocUsed) maybe?
Chris
next prev parent reply other threads:[~2005-04-27 17:46 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
2005-04-27 17:20 ` Robert Love
2005-04-27 17:44 ` Chris Friesen [this message]
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=426FCF7B.5020806@nortel.com \
--to=cfriesen@nortel.com \
--cc=dedekind@oktetlabs.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.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