Subject: Re: why is it not allowed to add a new socket protocol family as an external module?

From: Chris Friesen <[email-masked]>
Date: Wed, 20 Feb 2013 18:44:50 -0600

On 02/20/2013 05:23 PM, Stephen Hemminger wrote:
> On Wed, 20 Feb 2013 10:56:13 -0600
> Chris Friesen<[email-masked]>  wrote:
>
>> Hi,
>>
>> I was just wondering why the kernel doesn't allow a new network protocol
>> family to be loaded as as a kernel module built outside the kernel
>> source tree.

> If you want an answer, to the question, use a tool like cscope and
> learn to read the kernel code. There are several tables of pointers sized by NPROTO.

That's a bit insulting, don't you think?

Yes, there are a number of tables sized by NPROTO/AF_MAX/PF_MAX (and the 
fact that we use all three within the kernel is kind of sad) but there 
is no technical reason why we couldn't extend those dynamically if 
desired (with a linked list of additional protocols, perhaps).

Hence my question--is the restriction for an ideological reason or 
simply because nobody thought it was worth the effort?

Chris