All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@pps.jussieu.fr>
To: "L. Aaron Kaplan" <aaron@lo-res.org>
Cc: tmplab@lists.tmplab.org,
	The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>,
	olsr-users@lists.olsr.org, battlemesh@ml.ninux.org,
	babel-users@lists.alioth.debian.org
Subject: Re: [B.A.T.M.A.N.] [Babel-users]  WBMv3: a Babel perspective
Date: Sat, 12 Jun 2010 14:04:02 +0200	[thread overview]
Message-ID: <87ljaka24t.fsf@pirx.pps.jussieu.fr> (raw)
In-Reply-To: <0FE97F6D-EAF6-4E7D-BB15-1917CBB2813E@lo-res.org>

[Followups restricted to just olsr-users and babel-users.]

>> (1) when the network is broken, Babel is the first to collapse;
>> (2) Babel behaves well when the network is usable;

> Could you be a bit more specific with "usable"?? What does that mean
> regarding packetloss?

If you look at Elektra's writeup, in the first test none of the
protocols achieved more than 18% success -- and that's *after*
link-layer ARQ.  In the second test the figure was 27%.

In the third test, everyone achieved around 75% (after ARQ), which
I think is still pretty marginal, but starts becoming usable.

Perhaps Henning or Elektra can tell us what was the ETX (or,
equivalently, pre-ARQ packet loss) of the productive links in those
tests.

>> (3) Babel generates too many small packets on broken networks.

> Which creates more collisions in the air I assume ;-)

Well, it's still just 30 packets/s (as measured, all nodes added up),
which is well within what 802.11 is designed to handle.  (See Elektra's
slide number 8.)

> yeah ;-) Wish I had been there..

So do I.

                                        Juliusz

      reply	other threads:[~2010-06-12 12:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-11 18:32 [B.A.T.M.A.N.] WBMv3: a Babel perspective Juliusz Chroboczek
2010-06-12 11:36 ` L. Aaron Kaplan
2010-06-12 12:04   ` Juliusz Chroboczek [this message]

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=87ljaka24t.fsf@pirx.pps.jussieu.fr \
    --to=jch@pps.jussieu.fr \
    --cc=aaron@lo-res.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=babel-users@lists.alioth.debian.org \
    --cc=battlemesh@ml.ninux.org \
    --cc=olsr-users@lists.olsr.org \
    --cc=tmplab@lists.tmplab.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.