From: Manfred Spraul <manfred@colorfullife.com>
To: John Bucy <bucy@gloop.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nvidia and rmap (again)
Date: Thu, 22 Jul 2004 23:00:11 +0200 [thread overview]
Message-ID: <41002ADB.6000408@colorfullife.com> (raw)
John wrote:
>I don't quite know how to divine the right info out of slabinfo;
>I've attached it below.
>
If you search for a leak then you'd have to check the first number in
each row: the number of active objects. Just look at the first row: it
documents the fields in the following rows.
If a number is huge and constantly increasing, then there is would be a
leak. Typically the inode, dentry and buffer_head caches are large, the
rest are small.
But: slab manages only small objects. I assume that nvidia allocates
pages with alloc_pages() and then plays with the page flags. This is the
layer below slab, you must look at /proc/meminfo to detect leaks.
--
Manfred
next reply other threads:[~2004-07-22 20:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 21:00 Manfred Spraul [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-22 17:54 nvidia and rmap (again) John Bucy
2004-07-22 18:08 ` Dave Jones
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=41002ADB.6000408@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=bucy@gloop.org \
--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