public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Jay Brussels" <jay@dslx.net>
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.] Current OpenWrt build
Date: Wed, 12 Nov 2014 07:47:10 -0500	[thread overview]
Message-ID: <069201cffe76$c6b720c0$54256240$@dslx.net> (raw)

Antonio,

I am planning to start programming Ubiquiti and TP-Link Routers in two weeks for a very large BATMAN mesh deployment.

Although many patches I have seen on this list involves multicast traffic I have seen some others.  

Is the current OpenWrt release stable enough for deployment or are there some "must have" patches requiring a build from scratch for a successful deployment?


Jay Brussels
President
DSL Express
954-757-3254 
jay@dslx.net





-----Original Message-----
From: B.A.T.M.A.N [mailto:b.a.t.m.a.n-bounces@lists.open-mesh.org] On Behalf Of Krishnathiepan Rasanayagam
Sent: Wednesday, November 12, 2014 6:51 AM
To: The list for a Better Approach To Mobile Ad-hoc Networking
Subject: Re: [B.A.T.M.A.N.] Threads in batman-adv

yep. i should have :)
now only freading it out. sorry

thanks alot for replying :)

On Wed, Nov 12, 2014 at 2:47 PM, Antonio Quartulli <antonio@meshcoding.com> wrote:
>
>
> On 12/11/14 09:19, Krishnathiepan Rasanayagam wrote:
>> Hi All,
>>
>> Has anyone considered using threads in batman-adv?
>
> did you mean kthread? I don't think this would bring any real benefit.
> You should probably read/understand the rest of the networking stack 
> in the linux kernel to understand how incoming/outgoing packets are handled.
>
>> is is possible to use fork() send.c file?
>
> fork() is a function that is supposed to be used in *userspace* to 
> create a new *process*.
> This is neither available nor conceptually possible in kernel space.
>
> Maybe you should read a bit more about what you can do and what you 
> cannot do while developing a kernel module? :)
>
> --
> Antonio Quartulli
>



--
Best regards,
Krishna.


             reply	other threads:[~2014-11-12 12:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-12 12:47 Jay Brussels [this message]
2014-11-12 13:54 ` [B.A.T.M.A.N.] Current OpenWrt build Bastian Bittorf
2014-11-13 15:30   ` Jay Brussels
2014-11-15 18:58     ` Sven Eckelmann
2014-11-16  6:28       ` Linus Lüssing
2014-11-16  8:50         ` Sven Eckelmann
2014-11-16  9:14           ` Sven Eckelmann
2014-11-16 10:19             ` Linus Lüssing
2014-11-16  6:51 ` Linus Lüssing

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='069201cffe76$c6b720c0$54256240$@dslx.net' \
    --to=jay@dslx.net \
    --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