public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: syed moulana <syedmoulana47@gmail.com>
Subject: Re: [B.A.T.M.A.N.] batman-adv bonding feature - unable to get data packets fragmented into multiple wireless interfaces
Date: Fri, 10 Oct 2014 21:03:14 +0200	[thread overview]
Message-ID: <5383000.xXB04C6BSt@prime> (raw)
In-Reply-To: <CAKKX4kEYFJoSQLndrvP7E1pYP7PehPitWkTjv38bEG9iT-tjng@mail.gmail.com>

Hey Syed,

which version of batman-adv are you using?

Please note there is a fix for a bonding problem which hasn't been merged yet, 
please merge it manually for your tests (assuming you are using a recent 
version)

https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2014-August/012382.html

Also bonding has nothing to do with fragmentation - the idea of bonding is 
that the packets should not be split, but get sent interleaved over the 
interfaces, e.g. 

 * wlan 1 - packet 1
 * wlan 2 - packet 2
 * wlan 1 - packet 3
 * wlan 2 - packet 4
 * etc ...

To have a real gain from that, the two links must be equally good quality. 
Also deep queues in the driver may cause reordering of packets which will 
upset TCP. The best results I've seen in the past were 50% performance gain 
over a single link, but I didn't try it out in real world scenarios lately.

Thanks,
    Simon
On Tuesday 07 October 2014 17:27:50 syed moulana wrote:
> hi
> 
> I tested the throughput between point to point mesh nodes using single
> and 2 radios.
> 
> 1.  Using single radio (ch 5180)  the resulting throughput for HT40+
>            TCP max 250mbit/s
>            UDP - max 320mbit/s
> 
> 2. Using 2 radios with and without batctl bonding enabled (ch 5180 for
> wlan0, ch 5785 for wlan1), the resulting throughput for HT40+ is same.
>            with batctl bonding and fragmentation enabled I believed I
> should be getting 50% gain in througput.
>     When I monitor the wlan0 and wlan1 interfaces using batctl tcpdump
> -p 4 wlanx I can see that iperf data are interleaved.
>     There is no splitting of data frames into 2 wireless interfaces.
> 
> Please advice
> 
> Tq
> 
> Syed


  reply	other threads:[~2014-10-10 19:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07  9:27 [B.A.T.M.A.N.] batman-adv bonding feature - unable to get data packets fragmented into multiple wireless interfaces syed moulana
2014-10-10 19:03 ` Simon Wunderlich [this message]
2014-10-10 21:28   ` Ray Gibson
     [not found] <d45jj1bb42of1liops4p7fi7.1413160019506@email.android.com>
2014-10-13 10:52 ` Simon Wunderlich

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=5383000.xXB04C6BSt@prime \
    --to=sw@simonwunderlich.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=syedmoulana47@gmail.com \
    /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