From: Ignacio Quezada <dreamtrick@gmail.com>
To: "b.a.t.m.a.n" <b.a.t.m.a.n@lists.open-mesh.org>
Subject: [B.A.T.M.A.N.] is the multicast performance throttled?
Date: Thu, 11 Aug 2016 17:13:01 +0200 [thread overview]
Message-ID: <1470928381.10121.0.camel@gmail.com> (raw)
Hello,
I am trying to build an application using UDP multicast sockets based
on a network mesh built with devices connected in IBSS mode.
The kernel documentation says that this was the place to ask questions
or anything :).
Testing the application in the mentioned environment, it suffers some
kind of throttling or buffering limiting the throughput. Testing with
my application, without the batman interface, just 2 IBSS connected
devices, the multicast rate goes around 100kb/s (not saying that the
wifi link actually tops at that speed), but then just to add the
batman-adv interface and use that instead, the multicast rate becomes
unstable between 0-20kb/s.
Disabling multicast optimization, it changes a bit the behaviour but
still the same speed.
If I change the multicast packet to a unicast packet, both setups
achieve the same speed (~100kb/s), so the batman interface is working
but the multicast packets are being handled in a different way. Is it
supposed to be like that?
The packets are sent right away according to the iptables counter of
packets as well as tcpdump, but the receiver only gets them in a very
slow way (counting but not calculating, I think it is around 8 packets
per second).
The MTU is set as advised, 1532 and the payload for the UDP packets is
as big as it can be so the packet does not get fragmented.
Any way to increase the rate or disabling the throttling?
--
MVH
Ignacio Quezada
next reply other threads:[~2016-08-11 15:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 15:13 Ignacio Quezada [this message]
2016-08-11 15:47 ` [B.A.T.M.A.N.] is the multicast performance throttled? Linus Lüssing
2016-08-11 16:09 ` Ignacio Quezada
2016-08-11 16:31 ` Linus Lüssing
2016-08-12 7:50 ` Ignacio Quezada
2016-08-14 17:21 ` Linus Lüssing
2016-08-14 17:28 ` Linus Lüssing
2016-08-15 18:03 ` Ignacio Quezada
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=1470928381.10121.0.camel@gmail.com \
--to=dreamtrick@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;
as well as URLs for NNTP newsgroup(s).