Date: Fri, 17 Jan 2014 08:10:52 -0800 From: Luigi Rizzo <rizzo@iet.unipi.it> To: "Alexander V. Chernikov" <melifaro@freebsd.org> Cc: FreeBSD Current <current@freebsd.org> Subject: Re: picking a new AF_* number for NETLINK ? Message-ID: <CA%2BhQ2%2BiPSxdb3166Cvx%2Be7PABds=qg-37yeTzpvmQE-rv%2BN5eg@mail.gmail.com> In-Reply-To: <52D95305.6020909@FreeBSD.org> References: <20140116231902.GA51955@onelab2.iet.unipi.it> <52D95305.6020909@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 17, 2014 at 7:57 AM, Alexander V. Chernikov < melifaro@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BhQ2%2BiPSxdb3166Cvx%2Be7PABds=qg-37yeTzpvmQE-rv%2BN5eg>