From: Philipp Psurek <philipp.psurek@gmail.com>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] batctl: page allocation failure
Date: Sun, 28 Feb 2016 17:55:54 +0100 [thread overview]
Message-ID: <1456678554.1958.40.camel@gmail.com> (raw)
In-Reply-To: <20160228132736.GI5481@otheros>
Hi Linus,
thank you for your answer. (Un)fortunately I can not reproduce the page
allocation failure any more after adding one more Batman device to the
Ethernet or moving some files through NFS.
Am Sonntag, den 28.02.2016, 14:27 +0100 schrieb Linus Lüssing:
[…]
> PS: How much (free and in total) RAM does your device have, which
> device is
The ARM device is a Cubieboard with Allwinner A20 CPU and 1 GiB RAM.
The RAM usage was not different to this output [1], but I can not
assure this. Anyway the system has plenty of RAM and was idle
> it exactly? Just that others know how much RAM is needed to read
> from debugfs with a 300+ nodes setup right now.
There is no problem watching the originators on an 32 MiB RAM OpenWrt
router with 3.10.49 mips.
I'm sorry bothering you with this issue. Have a lot of fun developing
B.A.T.M.A.N. advanced.
Best regards,
Philipp
[1] # cat /proc/meminfo
MemTotal: 1011224 kB
MemFree: 18044 kB
Buffers: 61100 kB
Cached: 825416 kB
SwapCached: 0 kB
Active: 383532 kB
Inactive: 548588 kB
Active(anon): 24220 kB
Inactive(anon): 21984 kB
Active(file): 359312 kB
Inactive(file): 526604 kB
Unevictable: 0 kB
Mlocked: 0 kB
HighTotal: 270336 kB
HighFree: 988 kB
LowTotal: 740888 kB
LowFree: 17056 kB
SwapTotal: 4194300 kB
SwapFree: 4194300 kB
Dirty: 1580 kB
Writeback: 0 kB
AnonPages: 45656 kB
Mapped: 3844 kB
Shmem: 616 kB
Slab: 47596 kB
SReclaimable: 37300 kB
SUnreclaim: 10296 kB
KernelStack: 792 kB
PageTables: 1004 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 4699912 kB
Committed_AS: 117352 kB
VmallocTotal: 245760 kB
VmallocUsed: 14052 kB
VmallocChunk: 212928 kB
next prev parent reply other threads:[~2016-02-28 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 23:39 [B.A.T.M.A.N.] batctl: page allocation failure Philipp Psurek
2016-02-28 13:27 ` Linus Lüssing
2016-02-28 16:45 ` Matthias Schiffer
2016-02-28 16:55 ` Philipp Psurek [this message]
2016-02-28 16:23 ` Sven Eckelmann
2016-02-28 17:06 ` Sven Eckelmann
2016-02-28 17:38 ` Philipp Psurek
2016-02-28 17:42 ` Philipp Psurek
2016-02-28 17:54 ` Sven Eckelmann
2016-02-28 17:17 ` Philipp Psurek
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=1456678554.1958.40.camel@gmail.com \
--to=philipp.psurek@gmail.com \
--cc=b.a.t.m.a.n@lists.open-mesh.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