All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@novell.com>
To: Chris Friesen <cfriesen@nortel.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 13:20:38 -0400	[thread overview]
Message-ID: <1114622438.10836.8.camel@betsy> (raw)
In-Reply-To: <426FC46C.4070306@nortel.com>

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.

	Robert Love



  reply	other threads:[~2005-04-27 17:24 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 [this message]
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=1114622438.10836.8.camel@betsy \
    --to=rml@novell.com \
    --cc=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.