From: Mulyadi Santosa <mulyadi.santosa@gmail.com>
To: Naruto Nguyen <narutonguyen2018@gmail.com>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: How to detect slab memory leak
Date: Tue, 18 Dec 2018 14:42:13 +0700 [thread overview]
Message-ID: <CAGdaadbpNaSQDWaF=opwuSpGxpriwsZqxNXXSvwr-TUzkyOnUA@mail.gmail.com> (raw)
In-Reply-To: <CANpxKHH-PFW_7zbjPEjNU-iwhkhzxM6ZLtcCtLk53aFobrBSkQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 855 bytes --]
On Sun, Dec 16, 2018 at 1:25 PM Naruto Nguyen <narutonguyen2018@gmail.com>
wrote:
> Hi everyone,
>
> When using slabtop to display the cache size growing, I see that
> kmalloc-1024 and kmalloc-256 are increasing about 200MB after 1 hour.
> Is there any way to detect which kernel components cause this slab
> increase?
>
> Thanks a lot,
> Brs,
> Naruto
>
>
Hello Naruto
I think you can do it by instrumenting call to kmalloc(). These days, eBPF
is the hot stuff to try for this matter. See if it fits yours too.
regards,
Mulyadi
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
[-- Attachment #1.2: Type: text/html, Size: 1827 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2018-12-18 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 6:23 How to detect slab memory leak Naruto Nguyen
2018-12-18 7:42 ` Mulyadi Santosa [this message]
2018-12-18 8:31 ` Harsh Jain
2018-12-19 11:58 ` Naruto Nguyen
2018-12-21 7:32 ` Mulyadi Santosa
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='CAGdaadbpNaSQDWaF=opwuSpGxpriwsZqxNXXSvwr-TUzkyOnUA@mail.gmail.com' \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=narutonguyen2018@gmail.com \
/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).