From: Marcel Holtmann <marcel@holtmann.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-kernel@vger.kernel.org, Kevin Hayes <kevin@atheros.com>,
Jouni Malinen <j@w1.fi>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: Existing netlink kernel <--> kernel communication
Date: Mon, 17 Aug 2009 14:04:33 -0700 [thread overview]
Message-ID: <1250543073.30166.100.camel@localhost.localdomain> (raw)
In-Reply-To: <43e72e890908171137v73732ea3g957e574eae3a81d8@mail.gmail.com>
Hi Luis,
> Was curious if there are existing use cases of netlink for kernel <-->
> kernel communication rather than the typical kernel <--> userspace.
> The original RFC 3549 [1] does specify it could have been used for
> "intra-kernel messaging", but am just not aware of existing use cases.
> A pointer could help.
I would use direct function calls for kernel to kernel communication. No
need to put any messaging system in between.
Regards
Marcel
next prev parent reply other threads:[~2009-08-17 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 18:37 Luis R. Rodriguez
2009-08-17 21:04 ` Marcel Holtmann [this message]
[not found] <1279555620.2156.8538.camel@tng>
2010-07-19 18:54 ` Luis R. Rodriguez
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=1250543073.30166.100.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=kevin@atheros.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@gmail.com \
/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
all inboxes | Powered by JetHome®