All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@c0d3.blue>
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.] is the multicast performance throttled?
Date: Thu, 11 Aug 2016 17:47:23 +0200	[thread overview]
Message-ID: <20160811154723.GJ4483@otheros> (raw)
In-Reply-To: <1470928381.10121.0.camel@gmail.com>

Hi Ignacio,

Could you describe your setup a little more, just two devices?
What hardware are you using, which wifi cards? Which operating
system and version?

Which version of batman-adv are you using? What is your kernel
version?

What is a typical bitrate your wifi cards are agreeing on (iw
station dump)? What multicast rate have you configured for your
wifi cards?

What software are you using for testing? What is the bitrate you
have configured in there? Is the unicast test UDP as well? What
bitrates are you able to achieve via TCP? Does a lower payload
length make any difference?

Regards, Linus


On Thu, Aug 11, 2016 at 05:13:01PM +0200, Ignacio Quezada wrote:
> 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

  reply	other threads:[~2016-08-11 15:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 15:13 [B.A.T.M.A.N.] is the multicast performance throttled? Ignacio Quezada
2016-08-11 15:47 ` Linus Lüssing [this message]
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=20160811154723.GJ4483@otheros \
    --to=linus.luessing@c0d3.blue \
    --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 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.