linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Nico Schottelius <nico-kernel20120920@schottelius.org>,
	Arend van Spriel <arend@broadcom.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Dave Kleikamp <shaggy@kernel.org>,
	jfs-discussion@lists.sourceforge.net
Subject: Re: Out of memory on 3.5 kernels
Date: Mon, 24 Sep 2012 15:43:27 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1209241538310.6356@chino.kir.corp.google.com> (raw)
In-Reply-To: <20120921194931.GA732@schottelius.org>

On Fri, 21 Sep 2012, Nico Schottelius wrote:

>  Active / Total Objects (% used)    : 1165130 / 1198087 (97.2%)
>  Active / Total Slabs (% used)      : 81027 / 81027 (100.0%)
>  Active / Total Caches (% used)     : 69 / 101 (68.3%)
>  Active / Total Size (% used)       : 1237249.81K / 1246521.94K (99.3%)
>  Minimum / Average / Maximum Object : 0.01K / 1.04K / 15.23K
> 
>   OBJS ACTIVE  USE OBJ SIZE  SLABS OBJ/SLAB CACHE SIZE NAME                   
> 993607 993607 100%    1.21K  75358       26   2411456K jfs_ip

Well that doesn't look good.  100% of the inode cache for jfs are being 
used which either means

 - there's a memory leak, or

 - there's some sort of throttling issue in jfs.

And those objects are consuming ~2.3GB of slab on your 4GB machine and 
seems to only have occurred between v3.4.2 to v3.5.3.

It would be interesting to see what kmemleak would tell us.

Adding Dave Kleikamp to the cc.

  parent reply	other threads:[~2012-09-24 22:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 13:52 Out of memory on 3.5 kernels Arend van Spriel
2012-09-21 19:49 ` Nico Schottelius
2012-09-21 21:02   ` Fwd: " Arend van Spriel
2012-09-24 22:43   ` David Rientjes [this message]
2012-09-25 15:07     ` Dave Kleikamp
2012-09-26  6:03       ` Nico Schottelius
2012-09-26  6:06     ` Nico Schottelius
2012-09-26  8:57       ` Nico Schottelius
2012-09-27  5:52         ` Nico Schottelius
2012-10-03 21:23           ` Nico Schottelius
2012-10-05 15:48             ` Valdis.Kletnieks
2012-10-05 17:51               ` Nico Schottelius
2012-10-30 10:35                 ` Nico Schottelius
2012-11-01 18:04                   ` [Jfs-discussion] " Tino Reichardt
2012-11-21 22:37                   ` Dave Kleikamp
2012-11-27 15:56                     ` [Jfs-discussion] " Dave Kleikamp
2012-11-27 16:11                       ` Nico Schottelius
  -- strict thread matches above, loose matches on Subject: below --
2012-09-20  6:02 Nico Schottelius
2012-09-20  6:54 ` David Rientjes
2012-09-20  7:32   ` Nico Schottelius
2012-09-20  7:44     ` Arend van Spriel
2012-09-20  8:21       ` Nico Schottelius
2012-09-20 12:12       ` Nico Schottelius

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=alpine.DEB.2.00.1209241538310.6356@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=arend@broadcom.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nico-kernel20120920@schottelius.org \
    --cc=shaggy@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;
as well as URLs for NNTP newsgroup(s).