Re: picking a new AF_* number for NETLINK ?
On Fri, Jan 17, 2014 at 12:19:02AM +0100, Luigi Rizzo wrote: In porting the kernel openvswitch code to FreeBSD we have implemented netlink sockets, so we need to pick a number to use for AF_NETLINK/PF_NETLINK in the messages. Obviously we'd like ovs to be loadable as a module on existing kernels, so i wonder if there are any restrictions on what we can use -- specifically, whether we should make sure that AF_NETLINK AF_MAX or that is irrelevant. I asked this question a couple of month ago to Alfred (who did the reservation stuff) exactly for AF_NETLINK which I planned to implement here is his answer: | You want to take 38. | | The next person should take 40. | | All odds until 133 are allocated for vendors and should not be used by FreeBSD | code. regards, Bapt pgpUQ5rzen58H.pgp Description: PGP signature
Re: picking a new AF_* number for NETLINK ?
On 17.01.2014 03:19, Luigi Rizzo wrote: In porting the kernel openvswitch code to FreeBSD we have implemented netlink sockets, so we need to pick a Wow, great! How deep you're planning to go with netlink support? E.g. sockets with NETLINK_GENERIC OVS-related CMDs, or NETLINK_ROUTE (and other families like FW) as well? number to use for AF_NETLINK/PF_NETLINK in the messages. Obviously we'd like ovs to be loadable as a module on existing kernels, so i wonder if there are any restrictions on what we can use -- specifically, whether we should make sure that AF_NETLINK AF_MAX or that is irrelevant. cheers luigi ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: picking a new AF_* number for NETLINK ?
On Fri, Jan 17, 2014 at 7:57 AM, Alexander V. Chernikov melif...@freebsd.org wrote: On 17.01.2014 03:19, Luigi Rizzo wrote: In porting the kernel openvswitch code to FreeBSD we have implemented netlink sockets, so we need to pick a Wow, great! How deep you're planning to go with netlink support? E.g. sockets with NETLINK_GENERIC OVS-related CMDs, or NETLINK_ROUTE (and other families like FW) as well? for the time being we focus on the ovs-related commands. Our initial prototype overloaded PF_ROUTE: if the first message on a socket carried a PF_NETLINK identifier then all subsequent i/o is routed to the netlink routines. However this required small changes to route.c so now we are going to do the real thing (using a PF_NETLINK domain). cheers luigi ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
