From: Dan Kegel <dkegel@ixiacom.com>
To: fleury@cs.auc.dk, linux-kernel <linux-kernel@vger.kernel.org>
Subject: allocating netlink families? (was: re: Announce: NetKeeper Firewall For Linux)
Date: Mon, 03 Nov 2003 16:43:20 -0800 [thread overview]
Message-ID: <3FA6F628.70305@ixiacom.com> (raw)
Emmanuel Fleury wrote:
> http://www.cs.auc.dk/~fleury/netkeeper/
Hey, that seems to be a nice example of how to write
a new netlink family. Thanks!
I see you're using NETLINK_USERSOCK. Netlink families
appear to be a precious commodity (netlink_dev.c, at
least, will break if you raise MAX_LINKS above 32).
Has there been any discussion of how one should pick
netlink family numbers for new stuff like netkeeper?
Sure, everyone could use NETLINK_USERSOCK, but
that means only one new netlink module could be resident at a time...
- Dan
next reply other threads:[~2003-11-03 23:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 0:43 Dan Kegel [this message]
2003-11-04 1:09 ` allocating netlink families? (was: re: Announce: NetKeeper Firewall For Linux) David S. Miller
2003-11-04 1:25 ` allocating netlink families? Dan Kegel
2003-11-04 8:47 ` allocating netlink families? (was: re: Announce: NetKeeper Firewall For Linux) Emmanuel Fleury
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=3FA6F628.70305@ixiacom.com \
--to=dkegel@ixiacom.com \
--cc=fleury@cs.auc.dk \
--cc=linux-kernel@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.