From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: [B.A.T.M.A.N.] reorganized kernel interface
Date: Sun, 28 Feb 2010 04:30:09 +0800 [thread overview]
Message-ID: <201002280430.09575.lindner_marek@yahoo.de> (raw)
Hi folks,
during the last batman developer meeting in Bruxelles we decided that it is
time to reorganize the batman-adv kernel interface to address numerous issues
and feature requests we have been hearing about throughout the last year. The
required changes are extensive, therefore it will take a while to get it all
sorted out.
Specifically we are targeting the following items:
* People with larger layer2 meshes have expressed the idea of having multiple
meshes running on the same device in order to build a node which sits
inbetween 2 (or more) mesh networks and routes the traffic from one to the other
(thereby reducing the overhead). Due to code limitations batman-adv can only
create a single mesh on a machine. There are numerous global variables and
functions that need to be modfied in order to support multiple meshes.
* Despite the fact that we have a growing number of events which would allow
user space applications to implement some intelligence to improve the mesh
experience batman-adv has no way of communicating these events back to
applications. To address this issue we will be moving batman-adv from /proc to
sysfs which empowers batman-adv to trigger uevents that can be handled from
user space.
* Since batman-adv's existence its parameter always were configurable using
simple commands like echo or cat. Although this interface was easy it is not
possible to direct error messages back to the shell, In case you misspelled a
parameter you had to check the system logs to learn about it. The following
patch introduces a way of exporting "allowed values", so that user space
applications can parse it and alert the user immediately. See batctl as an
example.
Please review and comment the following patches. As soon as those were
digested I will send more.
Known issues:
* When sending a wrong input value to aggregate_ogm or bonding the kernel
processes the input 3 times.
Cheers,
Marek
next reply other threads:[~2010-02-27 20:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 20:30 Marek Lindner [this message]
2010-02-27 20:30 ` [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: convert multiple /proc files to use sysfs Marek Lindner
2010-02-27 20:30 ` [B.A.T.M.A.N.] [PATCH 2/2] batctl: follow /proc to sysfs conversion & introduce input validation Marek Lindner
2010-03-01 1:51 ` Linus Lüssing
2010-03-01 6:06 ` Andrew Lunn
2010-03-01 7:17 ` Marek Lindner
2010-03-01 7:27 ` Marek Lindner
2010-02-28 9:37 ` [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: convert multiple /proc files to use sysfs Andrew Lunn
2010-02-28 10:19 ` Marek Lindner
2010-02-28 17:47 ` Gus Wirth
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=201002280430.09575.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@lists.open-mesh.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox