lkml.org 
[lkml]   [2010]   [Jul]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: Existing netlink kernel <--> kernel communication
On Mon, Jul 19, 2010 at 9:07 AM, Patrick McManus <mcmanus@ducksong.com> wrote:
> Hi Luis,
>
> I'm following up to a linux kernel post of yours back in December:
>
> http://marc.info/?l=linux-kernel&m=125053428528207&w=3
>
> Basically, I have the same interest - an internal netlink client to the
> qdisc interfaces.. I was wondering if you made any progress on the topic
> you could share? It seems maddening that netlink is promoted as an
> intra-kernel mechanism but it is non-obvious how to write a client..

The reason we at Atheros were considering it was a possible way to
communicate between two different subsystems, in our case Bluetooth
and 802.11. While it is technically possible to use netlink for such
purposes it introduces a layer of complexity which can be avoided by
just using direct exported routines, and by coordinating between the
two subsystems you need communication with.

So, the real question I think is why do you need a rigid API ? If
there is a good need, perhaps its a good idea, but so far I guess no
one simply has come up with one.

Luis


\
 
 \ /
  Last update: 2010-07-19 20:57    [W:0.275 / U:0.192 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site