From: Axel Neumann <axel@open-mesh.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] Memory leak
Date: Fri, 4 Jan 2008 21:24:18 +0100 [thread overview]
Message-ID: <200801042124.18425.axel@open-mesh.net> (raw)
In-Reply-To: <20080104105751.q5lswookggc040gk@webmail.ddmesh.de>
Hi,
perhaps the problem is not related to 2.4/2.6 kernels but to the thread
implementation of ulibc (used by openWrt). On your notebook you are probably
running glibc. Glibc correctly shows only one process and not one per running
thread.
The changing PID might be because of the tunnel thread which is restarted when
(re-)connecting to a GW.
I could not reproduce the high memory consumption but recognized that memory
usage increases slightly (e.g. when opening a verbose debug-level) and never
decreases again to its old value. I thought the used memory (as indicated by
ps and friends) is not freed until required by another program.
ciao,
axel
On Freitag 04 Januar 2008, Freifunk Dresden wrote:
> Hello,
>
> I have a problem where batman (rev871 and rev908) consumes more and
> more memory
> until the router has no memory.
> I have added the output of the "top" command and the command line
> arguments of my setup.
>
> (WRT 10-1).....wlan.......(wrt 10-2) =======tinc vpn=====(laptop debian
> 0-1) kernel 2.4.32 kernel 2.4.32 kernel 2.6
>
>
> I have seen that one batman thread changes the PID where the other
> stay the same.
> Below you will find the "top" output for batmand when it was started and
> after about one hour.
> The batmand running on kernal 2.6 does not increment its memory needs.
> Perhaps there are some allocation of memory that is not freed because of
> the arguments of the batmand.
> There is no special traffic on those nodes, they just are connected.
>
> Any Ideas?
> Regards
> Stephan
>
> linux 2.6. (0-1)
> /usr/bin/batmand -g 1024/200 -a 104.61.0.0/16 -a 141.56.20.5/32 -s
> 10.12.0.1 --no-unreachable-rule
> --no-throw-rules --no-prio-rules --resist-blocked-send wifi tbb /t 1 /i /A
> wifi is a unused bridge
> 1 batmand
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 6612 root 15 0 19136 684 532 S 0.3 0.1 0:27.85 batmand
>
> ####################################################################
>
> linux 2.4.32 (wrt GL 10-2)
> /sbin/batmand -s 10.12.0.1 -a 10.12.10.16/28 -r 2 --t 63
> --no-unreachable-rule --no-throw-rules --no-prio-rules
> --resist-blocked-send eth1 tbb /t 1 /i /A
>
> 3 batmands
> PID PPID USER STAT VSZ %MEM %CPU COMMAND
> 847 846 root S 1196 4% 0% /sbin/batmand -s 10.12.0.1
> -a 10.12.10.16/28 -r 2 --t 63 --no-unreachable-rule
> 3937 847 root S 1196 4% 0% /sbin/batmand -s 10.12.0.1
> -a 10.12.10.16/28 -r 2 --t 63 --no-unreachable-rule
> 848 847 root S 1196 4% 0% /sbin/batmand -s 10.12.0.1
> -a 10.12.10.16/28 -r 2 --t 63 --no-unreachable-rule
> ----------
> 848 847 root S 2076 7% 0% /sbin/batmand -s 10.12.0.1
> -a 10.12.10.16/28 -r 2 --t 63 --no-unreachable-rule
> 847 846 root S 2076 7% 0% /sbin/batmand -s 10.12.0.1
> -a 10.12.10.16/28 -r 2 --t 63 --no-unreachable-rule
> 22570 847 root S 2076 7% 0% /sbin/batmand -s 10.12.0.1
> -a 10.12.10.16/28 -r 2 --t 63 --no-unreachable-rule
>
>
> ####################################################################
>
> linux 2.4.32 (wrt GL 10-1)
> /sbin/batmand -s 10.12.0.1 -a 10.12.10.0/28 -r 2 --t 63
> --no-unreachable-rule --no-throw-rules --no-prio-rules
> --resist-blocked-send eth1
>
> 4 batmands
> PID PPID USER STAT VSZ %MEM %CPU COMMAND
> 837 1 root S 1292 9% 0% /sbin/batmand -s 10.12.0.1
> -a 10.12.10.0/28 -r 2 --t 63 --no-unreachable-rule -
> 838 837 root S 1292 9% 0% /sbin/batmand -s 10.12.0.1
> -a 10.12.10.0/28 -r 2 --t 63 --no-unreachable-rule -
> 11854 838 root S 1292 9% 0% /sbin/batmand -s 10.12.0.1
> -a 10.12.10.0/28 -r 2 --t 63 --no-unreachable-rule -
> 839 838 root S 1292 9% 0% /sbin/batmand -s 10.12.0.1
> -a 10.12.10.0/28 -r 2 --t 63 --no-unreachable-rule -
> ---------
> 837 1 root S 2172 15% 0% /sbin/batmand -s 10.12.0.1
> -a 10.12.10.0/28 -r 2 --t 63 --no-unreachable-rule -
> 838 837 root S 2172 15% 0% /sbin/batmand -s 10.12.0.1
> -a 10.12.10.0/28 -r 2 --t 63 --no-unreachable-rule -
> 30544 838 root S 2172 15% 0% /sbin/batmand -s 10.12.0.1
> -a 10.12.10.0/28 -r 2 --t 63 --no-unreachable-rule -
> 839 838 root S 2172 15% 0% /sbin/batmand -s 10.12.0.1
> -a 10.12.10.0/28 -r 2 --t 63 --no-unreachable-rule -
>
>
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
next prev parent reply other threads:[~2008-01-04 20:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 9:57 [B.A.T.M.A.N.] Memory leak Freifunk Dresden
2008-01-04 20:24 ` Axel Neumann [this message]
2008-01-05 20:47 ` Freifunk Dresden
2008-01-06 14:03 ` Axel Neumann
2008-01-06 15:52 ` Freifunk Dresden
2008-01-07 9:45 ` Axel Neumann
2008-01-07 12:56 ` Freifunk Dresden
2008-01-07 16:48 ` [B.A.T.M.A.N.] one-way / two-way tunnel (was: Memory leak) Axel Neumann
2008-01-07 20:52 ` Freifunk Dresden
2008-01-10 8:25 ` Freifunk Dresden
2008-01-17 13:04 ` [B.A.T.M.A.N.] Memory leak Freifunk Dresden
2008-01-20 11:13 ` Axel Neumann
2008-01-26 21:04 ` Freifunk Dresden
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=200801042124.18425.axel@open-mesh.net \
--to=axel@open-mesh.net \
--cc=b.a.t.m.a.n@open-mesh.net \
/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