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: Re: [B.A.T.M.A.N.] running batman-adv in a openvz VE
Date: Sun, 4 Apr 2010 10:58:33 +0800 [thread overview]
Message-ID: <201004041058.33336.lindner_marek@yahoo.de> (raw)
In-Reply-To: <201004040029.26465.sven.eckelmann@gmx.de>
On Sunday 04 April 2010 06:29:24 Sven Eckelmann wrote:
> Also we only use init_net in hard_interface.c when we add a
> interface - so the actual namespace should not be a problem. But I am a
> little bit curious why we only deactivate the interface in hard_if_event
> when it gets NETDEV_UNREGISTER. I would think that batman_if->net_dev of
> that interface isn't valid anymore and we aren't allowed to access it. So
> removing it should be the right choice.
The idea was to support some buggy (wifi) drivers better. Back in the layer 3
days I had a driver (not exactly sure which one) that would disappear for a
second and then come back immediately afterwards. In that case we don't want
to purge all routing information over and over again.
> I started to write some tests, but then noticed quite fast that (at least
> in 0.2.1) all variables to store the proc filesystem information are
> global variables - which will not work.
Yes, this is why I mentioned the multiple mesh support in one of my earlier
mails. The current stable module (0.2.x) is pretty static and cluttered with
global variables which I started to clean up.
On the other hand I don't think it is worthwhile to invest much time into the
proc-fs implementation since it is phasing out. I even thought about
backporting the sysfs patches to the 0.2.2 branch, so that we can have all
kernel interface changes while batman-adv resides in the staging tree. Later
it will be much harder.
Regards,
Marek
next prev parent reply other threads:[~2010-04-04 2:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 9:37 [B.A.T.M.A.N.] running batman-adv in a openvz VE Bjoern Franke
2010-04-03 9:54 ` Sven Eckelmann
2010-04-03 12:43 ` Bjoern Franke
2010-04-03 16:41 ` Sven Eckelmann
2010-04-03 22:29 ` Sven Eckelmann
2010-04-04 2:58 ` Marek Lindner [this message]
2010-04-03 9:57 ` Marek Lindner
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=201004041058.33336.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;
as well as URLs for NNTP newsgroup(s).