mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pietro Paolini <pulsarpietro@aol.com>
To: linux-kernel@vger.kernel.org
Subject: /proc/slab_allocators question
Date: Thu, 3 Apr 2014 14:02:20 -0400 (EDT)	[thread overview]
Message-ID: <8D11D7DFDC0DCD5-1BF8-2054F@webmail-va038.sysops.aol.com> (raw)
In-Reply-To: <533D9F8A.6030001@pobox.com>

 Hello everyone,

I am experiencing a problem where the system reboot due low memory 
conditions and looking at the
/proc/slabinfo

I am able to see that a lot of memory is being used by the size-1024 
cache name which reports a high number of active objects, then
in order to debug this situation I tried to compile with :

CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_SLAB_LEAK=y

Now I am able to cat the /proc/slab_allocators leaf but that name, nor 
either all the size-* - are present
in that output, I guess because that memory is used by the kmalloc() 
functions.

Than how can I trace who allocates  all that memory in my system ?

Best Regards,
Pietro

  reply	other threads:[~2014-04-03 18:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03 16:33 linux-3.14 nfsd regression Mark Lord
2014-04-03 16:44 ` Mark Lord
2014-04-03 16:53   ` Mark Lord
2014-04-03 17:16 ` J. Bruce Fields
2014-04-03 17:51   ` Mark Lord
2014-04-03 18:02     ` Pietro Paolini [this message]
2014-04-03 18:55     ` Jeff Layton
2014-04-03 20:16       ` J. Bruce Fields
2014-04-03 23:21         ` Jeff Layton
2014-04-04 13:58           ` J. Bruce Fields
2014-04-04 14:07             ` Jeff Layton
2014-05-01 11:50             ` Mark Lord
2014-05-01 19:59               ` J. Bruce Fields
2014-04-03 19:30     ` J. Bruce Fields
2014-04-03 20:11       ` J. Bruce Fields
2014-04-03 20:48       ` Mark Lord
2014-04-03 21:28         ` J. Bruce Fields
2014-04-03 21:32           ` Mark Lord
2014-04-03 20:15     ` J. Bruce Fields
2014-04-03 20:51       ` Mark Lord

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=8D11D7DFDC0DCD5-1BF8-2054F@webmail-va038.sysops.aol.com \
    --to=pulsarpietro@aol.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 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®