netdev
[Top] [All Lists]

Re: Allowing netlink_family to be any integer (was: [PATCH 2.6] iptables

To: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Subject: Re: Allowing netlink_family to be any integer (was: [PATCH 2.6] iptables CLUSTERIP target)
From: Thomas Graf <tgraf@xxxxxxx>
Date: Fri, 22 Oct 2004 00:53:15 +0200
Cc: Harald Welte <laforge@xxxxxxxxxxxxx>, lmb@xxxxxxx, ahu@xxxxxxx, hch@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx, davem@xxxxxxxxxxxxx
In-reply-to: <E1CKkWZ-0005x5-00@xxxxxxxxxxxxxxxxxxxxxxxx>
References: <20041021142527.GG3551@xxxxxxxxxxxxxxxxxxxxxxx> <E1CKkWZ-0005x5-00@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
* Herbert Xu <E1CKkWZ-0005x5-00@xxxxxxxxxxxxxxxxxxxxxxxx> 2004-10-22 07:31
> Initially I considered an interface where kernel users can register
> themselves using a string as the key.  But I soon realised that we
> could simply allow the netlink_family field to be an arbitrary integer
> that is used as a key to a hash table.

Sounds like a good idea, converting nl_table and nl_nonroot into
a hash table won't be much of a problem. The netlink device driver
must probably be changed to create devices on the fly if we want
modules to be able to register netlink families. The same goes
for some selinux stuff but this is minor.

The only real problem I see is sk_protocol being only 8bit as
limiting factor.

<Prev in Thread] Current Thread [Next in Thread>