public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] Hiding Local Topology ??? TTL
Date: Thu, 5 Mar 2009 14:58:32 +0100	[thread overview]
Message-ID: <20090305135831.GA1563@WGT634U> (raw)
In-Reply-To: <200903051422.15547.pmazart@web.de>

[-- Attachment #1: Type: text/plain, Size: 2115 bytes --]

On Thu, Mar 05, 2009 at 02:22:15PM +0100, P. Mazart wrote:
> Am Donnerstag, 5. März 2009 schrieb Marek Lindner:
> > This paper just mentions the possibilities - not all flavors
> > implement that feature. As far as I know bmx (batman-experimental)
> > supports it though.
> 
> Now I'm completely stuck with BM's brands. :-)
Please read http://open-mesh.net/wiki/BranchesExplained to understand basic
differences between the "brands". B.A.T.M.A.N.-adv has completely different
ideas about what to route. It is not meant as drop-in replacement and not
for any performance reasons. 

> Can you say something about overhead and performance of BM in 
> kernelspace compared to the udp-userspace deamon?
> And devel-status of each of them?
You can only compare batman-adv-kernelland and batman-adv-userspace
performance wise. Userspace has some performance problems and was meant to
test the concept of routing ethernet frames instead of creating routing
tables for ip routing.
B.A.T.M.A.N. (aka batmand) has no kernel space implementation, but a
supporting kernel module for it's gateway functionality. It should help
the gateway node to reduce the performance bottle neck by not copying all
data from kernelland to userspace.

If you would really compare batman-adv-kernelland and batmand then please
ask again - I don't have any good numbers here, but maybe somebody else
has.

If you really want to test batman-adv-kernelland then please use the
last stable release from 
 http://downloads.open-mesh.net/batman/stable/sources/batman-adv-kernelland/
and not the current version from svn. New experimental features were added
there recently and it is not in a stabilising phase at the moment.

> > […] The packets sent to the vis server are UDP packets […]
> 
> Ahh. Great. Thank's for the information.
If you want to check the amount of time between two vis packets:
 http://open-mesh.net/browser/trunk/batman/batman.c?annotate=blame&rev=1235#L1232
It is around 10000ms at the moment in batmand, but as Marek said it depends
on the implementation.

Best regards,
	Sven

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2009-03-05 13:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 20:26 [B.A.T.M.A.N.] Hiding Local Topology – TTL P. Mazart
2009-03-05 10:55 ` P. Mazart
2009-03-05 11:14   ` Marek Lindner
2009-03-05 13:22     ` P. Mazart
2009-03-05 13:29       ` P. Mazart
2009-03-05 13:58       ` Sven Eckelmann [this message]
2009-03-11 13:20         ` [B.A.T.M.A.N.] Hiding Local Topology ??? TTL P. Mazart
2009-03-11 21:51           ` Sven Eckelmann
2009-03-11 22:09             ` P. Mazart

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=20090305135831.GA1563@WGT634U \
    --to=sven.eckelmann@gmx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox