From: "David S. Miller" <davem@redhat.com>
To: Dan Kegel <dkegel@ixiacom.com>
Cc: fleury@cs.auc.dk, linux-kernel@vger.kernel.org
Subject: Re: allocating netlink families? (was: re: Announce: NetKeeper Firewall For Linux)
Date: Mon, 3 Nov 2003 17:09:35 -0800 [thread overview]
Message-ID: <20031103170935.5c6688b9.davem@redhat.com> (raw)
In-Reply-To: <3FA6F628.70305@ixiacom.com>
On Mon, 03 Nov 2003 16:43:20 -0800
Dan Kegel <dkegel@ixiacom.com> wrote:
> 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...
When it's determined to be useful and to be added to
the main kernel sources, we'll allocate a number.
Before that time, there is no need to allocate. We'd
run out quickly if everyone with a funny netlink thing they
wanted to do asked for a number.
next prev parent reply other threads:[~2003-11-04 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 0:43 allocating netlink families? (was: re: Announce: NetKeeper Firewall For Linux) Dan Kegel
2003-11-04 1:09 ` David S. Miller [this message]
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=20031103170935.5c6688b9.davem@redhat.com \
--to=davem@redhat.com \
--cc=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 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).