b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: 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, 3 Apr 2010 11:54:13 +0200	[thread overview]
Message-ID: <201004031154.19191.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <4BB70C4B.5000909@nord-west.org>

[-- Attachment #1: Type: Text/Plain, Size: 835 bytes --]

On Saturday 03 April 2010 11:37:15 Bjoern Franke wrote:
> is there any possibility to run batman-adv in a openvz VE?

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?

> Must it run
> as kernel module or is there any way to run it in userspace?

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).

Best regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2010-04-03  9:54 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 [this message]
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
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=201004031154.19191.sven.eckelmann@gmx.de \
    --to=sven.eckelmann@gmx.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).