From: Andi Kleen <andi@firstfloor.org>
To: Sven Eckelmann <sven.eckelmann@gmx.de>
Cc: netdev@vger.kernel.org, b.a.t.m.a.n@lists.open-mesh.net,
davem@davemloft.net
Subject: Re: [B.A.T.M.A.N.] [PATCHv4] net: Add batman-adv meshing protocol
Date: Wed, 08 Sep 2010 09:14:29 +0200 [thread overview]
Message-ID: <87sk1kiu5m.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1283646353-17811-1-git-send-email-sven.eckelmann@gmx.de> (Sven Eckelmann's message of "Sun, 5 Sep 2010 02:25:53 +0200")
Sven Eckelmann <sven.eckelmann@gmx.de> writes:
> B.A.T.M.A.N. (better approach to mobile ad-hoc networking) is a routing
> protocol for multi-hop ad-hoc mesh networks. The networks may be wired or
> wireless. See http://www.open-mesh.org/ for more information and user space
> tools.
It seems rather unusual to have the complete routing protocol in
kernel. And this is a lot of code. The normal way to do such things is
to have the routing policy etc. in a user daemon and only let the kernel
provide some services to this.
Could you elaborate a bit why this approach was not chosen?
I assume if it needs a switch it could have a switching "hot path" layer
in kernel and the policy somewhere else.
You write
> +Batman advanced was implemented as a Linux kernel driver to re-
> +duce the overhead to a minimum. It does not depend on any (other)
What overhead exactly?
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-09-08 7:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-05 0:25 [B.A.T.M.A.N.] [PATCHv4] net: Add batman-adv meshing protocol Sven Eckelmann
2010-09-07 17:19 ` Paul E. McKenney
2010-09-07 17:56 ` Sven Eckelmann
2010-09-07 18:10 ` Paul E. McKenney
2010-09-07 18:24 ` Sven Eckelmann
2010-09-08 7:14 ` Andi Kleen [this message]
2010-09-08 9:42 ` Sven Eckelmann
2010-09-08 18:22 ` Jesse Gross
2010-09-08 18:58 ` Sven Eckelmann
2010-09-08 19:54 ` Jesse Gross
2010-09-08 20:25 ` Sven Eckelmann
2010-09-08 20:42 ` Sven Eckelmann
2010-09-08 23:13 ` Justin Pettit
2010-09-08 23:37 ` Jesse Gross
2010-09-14 19:21 ` Simon Wunderlich
2010-09-08 19:12 ` Marek Lindner
2010-09-08 20:07 ` Jesse Gross
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=87sk1kiu5m.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sven.eckelmann@gmx.de \
/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