From: "Marcin Mirosław" <marcin@mejor.pl>
To: netfilter@vger.kernel.org
Subject: Re: [xtables-addons][solved] memory usage in module geoip (probably)
Date: Tue, 30 Oct 2012 10:56:37 +0100 [thread overview]
Message-ID: <508FA455.9050106@mejor.pl> (raw)
In-Reply-To: <4F19928A.7050005@mejor.pl>
W dniu 20.01.2012 17:12, Marcin Mirosław pisze:
> Hello!
> I've noticed high size of kmalloc-512/2048 on my vps after a one, two
> weeks of work. Example:
> OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME
> 83440 83411 99% 0.57K 5960 14 47680K kmalloc-512
> 21615 21604 99% 2.07K 1441 15 46112K kmalloc-2048
> 103776 103765 99% 0.31K 8648 12 34592K skbuff_head_cache
>
> I've done a little investigation (trial by error method) to discover
> which process keep data in kmalloc. It looks those kmalloc are used by
> modules from xtables-addons-1.39. I'm using ipset6, geoip, sysrq,
> tarpit. I greped sources for string "kmalloc", kmalloc is used by sysrq
> and geoip (in some other modules too but i don't use them).
>
> I'd like to ask is such usage of memory ok? Which module could take so
> much precious ram?:) (I suspect geoip). How much memory geoip can use in
> worse case (db with ipv4 and ipv6)? Can i freed this cache without
> reboot? (I tried flush rules, rmmod but without succes).
With xtables-addons-1.46 I don't have such issue, probably commit
4ff5a8fbf62b75b17194a5cd324c08b8fa0f08bf in TARPIT resolves my problem.
Thanks:)
prev parent reply other threads:[~2012-10-30 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 16:12 [xtables-addons] memory usage in module geoip (probably) Marcin Mirosław
2012-01-20 17:05 ` Jan Engelhardt
2012-01-20 20:18 ` Marcin Mirosław
2012-01-20 21:00 ` Jan Engelhardt
2012-01-22 20:38 ` Marcin Mirosław
2012-01-22 20:53 ` Marcin Mirosław
2012-01-24 12:04 ` Jan Engelhardt
2012-10-30 9:56 ` Marcin Mirosław [this message]
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=508FA455.9050106@mejor.pl \
--to=marcin@mejor.pl \
--cc=netfilter@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.