From: Bjoern Franke <bjo@nord-west.org>
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: Sat, 03 Apr 2010 14:43:52 +0200 [thread overview]
Message-ID: <4BB73808.8080105@nord-west.org> (raw)
In-Reply-To: <201004031154.19191.sven.eckelmann@gmx.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
thanks for your reply!
> I have never used openvz, but adjusted some protocols to deal with openvz
> aware kernels (which means that they used and checked their namespace - so
> nothing really fancy).
>
> What must be done for device drivers to make them work on OpenVZ? Have you
> tried it and where have found you problems?
OpenVZ-Containers use the same kernel as the host system and I can build
and load the module on the host, but I don't know how to access
/proc/net/batman-adv from within the container. The container uses a own
proc-fs.
> There was a proof-of-concept version of batman-adv running in userland. This
> work was abandoned in favor of the in kernel implementation (better
> integration/better latency/less overhead/.... - stuff which is even worse on
> embedded systems - see Linus comments on the tinc vpn throughput on DIR300).
Ah ok.
best regards
Bjoern
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAku3OAQACgkQazwuXcm17apu4gCggYD8pg+Spx8XIgRmB3MDa8c2
vV4Ani8LgXUXInXRm0pOZd9g9jtslE7J
=fu2x
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-04-03 12:43 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 [this message]
2010-04-03 16:41 ` Sven Eckelmann
2010-04-03 22:29 ` Sven Eckelmann
2010-04-04 2:58 ` Marek Lindner
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=4BB73808.8080105@nord-west.org \
--to=bjo@nord-west.org \
--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).