All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gus Wirth <gwirth79@gmail.com>
To: b.a.t.m.a.n@lists.open-mesh.net
Subject: Re: [B.A.T.M.A.N.] Any results from BattleMesh 2009?
Date: Thu, 05 Nov 2009 09:20:15 -0800	[thread overview]
Message-ID: <4AF3094F.3000705@gmail.com> (raw)
In-Reply-To: <20091105024904.GA29859@Linus-Debian>

On 11/04/2009 06:49 PM, Linus Lüssing wrote:
[snip]
> PS: Just out of curiosity and also because the reports are in
> progress right now, what kind of results are you expecting?

Things I'm curious about:

How was the mesh configured?

What tools did you use to test the mesh?

How does the mesh react to the addition of a node? How long does it take 
a new node to integrate itself into the mesh?

How does the mesh react to the removal of a node? How long does it take 
the mesh to react to the node removal?

How does the mesh handle interference? Did you have anything to generate 
interference for testing?

What tools were used to visualize the mesh? Any images available?

Results of throughput testing for one hop, two hop, etc.

What was the CPU load on the mesh nodes while relaying traffic? What 
were the nodes?

I'll probably have more questions later.

Gus

  reply	other threads:[~2009-11-05 17:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04 23:58 [B.A.T.M.A.N.] Any results from BattleMesh 2009? Gus Wirth
2009-11-05  2:49 ` Linus Lüssing
2009-11-05 17:20   ` Gus Wirth [this message]
2009-11-05 17:26     ` Steven Leeman
2009-11-06 10:17     ` L. Aaron Kaplan
2009-11-06 14:35       ` Benjamin Henrion
2009-11-06 14:48         ` L. Aaron Kaplan
2009-11-06 14:57           ` Benjamin Henrion
2009-11-06 15:12             ` Steven Leeman
2009-11-06 15:51             ` L. Aaron Kaplan
2009-11-05  9:52 ` Carcellelist

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=4AF3094F.3000705@gmail.com \
    --to=gwirth79@gmail.com \
    --cc=b.a.t.m.a.n@lists.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.