From owner-freebsd-current@FreeBSD.ORG Fri Jan 17 16:01:28 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9F6368E4 for ; Fri, 17 Jan 2014 16:01:28 +0000 (UTC) Received: from mail.ipfw.ru (mail.ipfw.ru [IPv6:2a01:4f8:120:6141::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 63BA01112 for ; Fri, 17 Jan 2014 16:01:28 +0000 (UTC) Received: from [2a02:6b8:0:401:222:4dff:fe50:cd2f] (helo=ptichko.yndx.net) by mail.ipfw.ru with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1W481T-000K1S-BJ; Fri, 17 Jan 2014 15:55:39 +0400 Message-ID: <52D95305.6020909@FreeBSD.org> Date: Fri, 17 Jan 2014 19:57:57 +0400 From: "Alexander V. Chernikov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: Luigi Rizzo , current@freebsd.org Subject: Re: picking a new AF_* number for NETLINK ? References: <20140116231902.GA51955@onelab2.iet.unipi.it> In-Reply-To: <20140116231902.GA51955@onelab2.iet.unipi.it> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jan 2014 16:01:28 -0000 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-unsubscribe@freebsd.org" >