From: Dave Chinner <david@fromorbit.com>
To: Roland Eggner <edvx1@systemanalysen.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [kmemleak report 1/2] kernel 3.1.6, x86_64: mm, xfs ?, vfs ?
Date: Mon, 6 Feb 2012 17:11:56 +1100 [thread overview]
Message-ID: <20120206061156.GA12836@dastard> (raw)
In-Reply-To: <20120120000800.GA24762@mobil.systemanalysen.net>
On Fri, Jan 20, 2012 at 01:08:00AM +0100, Roland Eggner wrote:
> With kernel 3.1.6 + cherry-picked “kmemleak: Handle percpu memory allocation” as
> suggested by Catalin Marinas, I get no significant changes to kmemleak reports,
> and e.g. following /proc/meminfo snapshots. I wonder, is such a huge slab
> memory normal? Is there anything else suspicious?
Having 200k inodes in memory when you have 20+ filesystems is
not unusual.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2012-02-06 6:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 22:29 [kmemleak report 0/2] kernel 3.1.6, x86_64 Roland Eggner
2012-01-15 22:37 ` [kmemleak report 1/2] kernel 3.1.6, x86_64: mm, xfs ?, vfs ? Roland Eggner
2012-01-20 0:08 ` Roland Eggner
2012-02-06 6:11 ` Dave Chinner [this message]
2012-01-15 22:38 ` [kmemleak report 2/2] kernel 3.1.6, x86_64: pm, acpi-cpufreq ? Roland Eggner
2012-01-17 16:53 ` [kmemleak report 0/2] kernel 3.1.6, x86_64 Catalin Marinas
2012-01-19 13:21 ` Roland Eggner
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=20120206061156.GA12836@dastard \
--to=david@fromorbit.com \
--cc=edvx1@systemanalysen.net \
--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;
as well as URLs for NNTP newsgroup(s).