From: Stanislav Meduna <stano@meduna.org>
To: linux-rt-users@vger.kernel.org
Subject: SLAB leaks filep in 3.4.13-rt21 with PREEMPT_RT_FULL
Date: Sat, 20 Oct 2012 17:48:09 +0200 [thread overview]
Message-ID: <5082C7B9.9010502@meduna.org> (raw)
Hi,
compiling a current (a few days back) linux-stable-rt.git
with PREEMPT_RT_FULL results in a significant memory leak.
Just repeating
cat /proc/meminfo | grep Unreclaim
shows the unreclaimable memory jumping in 4 - 12 kB steps.
sync ; echo 3 > /proc/sys/vm/drop_caches
does not help either, this is for sure a real leak.
Looking at the slabtop output the "filp" is responsible for
most of the allocations, but there are more, even the "pid"
is rising although the number of threads in the system stays
the same.
PREEMPT_LL and selecting the SLUB (which is the preferred
allocator but not available with PREEMPT_RT_FULL) solves the
problem. I did not test with LL and SLAB (yet - I think that
it is hardly improbable that the SLAB allocator is the reason).
I can't test with PREEMPT_RTB as this option looks even more
broken on my setup and oopses at root filesystem (ext3)
mounting so I do not have the logs and the beginning rolls
out of the console so I can't even photograph it :(
The machine is an industrial embedded PC running a Geode LX.
I did not change the kernel in any way except adding an own
module that was not loaded during the tests.
I am new to linux-rt and this list - is it OK to attach
full .config files?
Thanks
--
Stano
next reply other threads:[~2012-10-20 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 15:48 Stanislav Meduna [this message]
2012-10-20 19:30 ` SLAB leaks filep in 3.4.13-rt21 with PREEMPT_RT_FULL Thomas Gleixner
2012-10-22 16:10 ` Stanislav Meduna
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=5082C7B9.9010502@meduna.org \
--to=stano@meduna.org \
--cc=linux-rt-users@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).