From: David Miller <davem@davemloft.net>
To: fubar@us.ibm.com
Cc: netdev@vger.kernel.org
Subject: Re: Netlink usage question (for bonding comm with userspace)
Date: Mon, 25 Jan 2010 16:51:52 -0800 (PST) [thread overview]
Message-ID: <20100125.165152.132891922.davem@davemloft.net> (raw)
In-Reply-To: <15914.1264466901@death.nxdomain.ibm.com>
From: Jay Vosburgh <fubar@us.ibm.com>
Date: Mon, 25 Jan 2010 16:48:21 -0800
> I could, for this project, use a netlink_kernel_create and
> socket(AF_NETLINK) pair to perform the communication (presumably adding
> a NETLINK_BONDING or the like to <linux/netlink.h>).
This is no longer done, so that we don't have an issue with
running out of netlink sub-protocol numbers.
Instead use generic netlink, the IDs are allocated dynamically
and looked up via text strings which provides a better scheme
for namespace allocation.
next prev parent reply other threads:[~2010-01-26 0:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 0:48 Netlink usage question (for bonding comm with userspace) Jay Vosburgh
2010-01-26 0:51 ` David Miller [this message]
2010-01-26 1:14 ` Jay Vosburgh
2010-01-26 2:03 ` David Miller
2010-01-26 11:25 ` Patrick McHardy
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=20100125.165152.132891922.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fubar@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).