From: Philipp Psurek <philipp.psurek@gmail.com>
To: Sven Eckelmann <sven@narfation.org>, 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 18:42:24 +0100 [thread overview]
Message-ID: <1456681344.1958.64.camel@gmail.com> (raw)
In-Reply-To: <1456681096.1958.61.camel@gmail.com>
> this is interesting:
>
> batctl o | wc -l
> 9320
more interesting:
# while true; do batctl o | wc -l; done
9474
9474
[…]
# while true; do batctl o | sort -u | wc -l; done
1764
1427
1705
1746
1568
1559
1558
1543
1429
1441
1506
1415
1429
1544
1605
1457
1497
1428
1447
1443
1423
1422
1495
1424
1427
…
next prev parent reply other threads:[~2016-02-28 17:42 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
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 [this message]
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=1456681344.1958.64.camel@gmail.com \
--to=philipp.psurek@gmail.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=sven@narfation.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