All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Jon Loeliger <jdl@bigfootnetworks.com>
Cc: netdev@vger.kernel.org
Subject: Re: Using netlink for intra-kernel requests?
Date: Wed, 09 Dec 2009 14:33:48 +0100	[thread overview]
Message-ID: <87bpi8mfur.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1260308546.29528.27.camel@jdl-desktop> (Jon Loeliger's message of "Tue, 08 Dec 2009 15:42:26 -0600")

Jon Loeliger <jdl@bigfootnetworks.com> writes:
>
> I tried to read through some of the similar routing bits, but
> even they confess that they "should use netlink", but then doesn't.

That was the great plan at some point, but it never
happened.
>
> I feel like I am missing or don't know where to find the
> documentation for the intra-kernel netlink messaging.

I don't think the kernel uses intra kernel netlink normally,
just tends to call functions directly. That's more efficient
anyways.

-Andi
-- 
ak@linux.intel.com -- Speaking for myself only.

  reply	other threads:[~2009-12-09 13:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-08 21:42 Using netlink for intra-kernel requests? Jon Loeliger
2009-12-09 13:33 ` Andi Kleen [this message]
2009-12-09 16:41   ` Jon Loeliger

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=87bpi8mfur.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=jdl@bigfootnetworks.com \
    --cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.