public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Antonio Quartulli <antonio@meshcoding.com>
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.] Threads in batman-adv
Date: Wed, 12 Nov 2014 10:17:15 +0100	[thread overview]
Message-ID: <5463259B.2020704@meshcoding.com> (raw)
In-Reply-To: <CAEbDFcQegtyVxsHUYjF5NL8mrL62LdkQNWtNikLtscodsGG1Ow@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 708 bytes --]



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


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-12  8:19 [B.A.T.M.A.N.] Threads in batman-adv Krishnathiepan Rasanayagam
2014-11-12  9:17 ` Antonio Quartulli [this message]
2014-11-12 11:51   ` Krishnathiepan Rasanayagam

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=5463259B.2020704@meshcoding.com \
    --to=antonio@meshcoding.com \
    --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