spliting kernel ipfw source ? (also involves sctp)
Vadim Goncharov
vadim_nuclight at mail.ru
Thu Mar 12 04:21:52 PDT 2009
Hi Luigi Rizzo!
On Fri, 6 Mar 2009 17:10:28 +0100; Luigi Rizzo wrote about 'Re: spliting kernel ipfw source ? (also involves sctp)':
>>>>>>>Hi, I am planning to split netinet/ip_fw2.c in a number of smaller files
>>>>>>>to make it more manageable, and while i do this I would also like to
>>>>>>>move the files related to ipfw2 (namely ip_fw*c) to a better place. Any
>>>>>>>objection to moving them to sys/netinet/ipfw2 ? Also, I can't help
>>
>> [...]
>>
>>> To further clarify, my plan is the following:
>>
>>> - leave ip_fw.h and ip_dummynet.h in /sys/netinet in case
>>> userland code is dependent on their location;
>>> - create /sys/netinet/ipfw/ to hold the kernel .c files related to
>>> ipfw and possibly dummynet (and also their private headers if any);
>>
>> Exactly that and nothing more? I'm currently working on extending ipfw for
>> Foundation with userland interface will be changed (and I thinking about
>> introducing modules), what else do you plan to do?
> Generally speaking, the kernel/userland interface will remain
> unchanged both at binary and source level, which means no
> backward incompatible changes in the sockopt numbers and messages,
> and no changes in the location and userland-visible parts of
> the headers.
> In practical terms, ip_fw.h might lose the definition of
> struct ip_fw_args, or the prototypes for the various kernel
> functions. The #ifdef _KERNEL part of ip_dummynet.h should
> also go to some other file.
> If you want to contact me, on the list or offline, to discuss what
> you want to do or what kind of 'modules' (kernel or userland ?) are
> you thinking about, i'd be more than happy to help.
I do not know whether this will be polite to discuss in details while
Foundation has not yet announced my work :-/ I hope they'll do it in a week
or so... I could say that at least dynamic rules and userland API/ABI will
go under serious incompatible changes, so any your changing headers is OK,
but what do you want to change inside kernel *.c is interesting to me.
--
WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight at mail.ru
[Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight]
More information about the freebsd-arch
mailing list