All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: unlisted-recipients:; (no To-header on input)
Cc: Chris Friesen <cfriesen@nortel.com>, linux-kernel@vger.kernel.org
Subject: Re: any way to find out kernel memory usage?
Date: Wed, 27 Apr 2005 18:23:55 -0400	[thread overview]
Message-ID: <427010FB.4080706@rtr.ca> (raw)
In-Reply-To: <1114624035.10836.19.camel@betsy>

How about in your private kernel build (Chris),
instrument alloc_pages() and free_pages() to maintain
a simple running tally of GFP_KERNEL and GFP_ATOMIC
page allocation counts ?

I wonder if that would catch all kernel allocations?

Cheers

  reply	other threads:[~2005-04-27 22:30 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
2005-04-27 17:47         ` Robert Love
2005-04-27 22:23           ` Mark Lord [this message]
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=427010FB.4080706@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=cfriesen@nortel.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 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.