All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shane Chao <schao@changind.com>
To: b.a.t.m.a.n@open-mesh.net
Subject: [B.A.T.M.A.N.] Multiple radios to improve throughput
Date: Mon, 02 Jun 2008 16:33:44 -0700	[thread overview]
Message-ID: <48448358.4070505@changind.com> (raw)

Elektra,

Thank you for pointing out in May 08 that most embedded boards do not 
have enough CPU power to saturate the capacity of single radio link.  I 
was experimenting Batman in a straight line, three node configuration 
with the middle node having two radios so it doesn't have to switch 
between node 1 and node 3.  My configuration is as follows:

node 1          node 2          node 3
------          ------          ------
  ath0 <--ch 1--> ath0
                  ath1 <--ch 11-> ath0

When I ran iperf between node 1 and 3, I did not see any throughput 
improvements with either one or two radios in node 2. I even stopped 
Batman and manually setup the routes and the performance remains the 
same.  However, when I upgrade node 2 from a 200MHz CPU board to a 
500MHz CPU board, the bandwidth went up 50%.  So thanks again for 
pointing out my bottleneck:)

Lastly, can someone suggest some embedded boards fast enough to push 
wifi radios to its limits?

Thanks,
Shane

             reply	other threads:[~2008-06-02 23:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02 23:33 Shane Chao [this message]
2008-06-03  8:24 ` [B.A.T.M.A.N.] Multiple radios to improve throughput Predrag Balorda
2008-06-05 12:39   ` Mark Kelly
2008-06-05 13:17     ` Benjamin Henrion
2008-06-05 13:43       ` Aaron Kaplan
2008-06-03  8:26 ` Predrag Balorda
2008-06-03 23:30 ` Benjamin Henrion
2008-06-03 23:41   ` cao jing
2008-06-12  3:53 ` Shane Chao
2008-06-12  8:43   ` Benjamin Henrion
  -- strict thread matches above, loose matches on Subject: below --
2008-05-14  1:21 Shane Chao
2008-05-14  2:55 ` elektra
2008-05-14  4:31   ` David Murray

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=48448358.4070505@changind.com \
    --to=schao@changind.com \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /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.