From owner-freebsd-current@FreeBSD.ORG Thu Jan 16 23:16:45 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4F5164A3 for ; Thu, 16 Jan 2014 23:16:45 +0000 (UTC) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 121A71352 for ; Thu, 16 Jan 2014 23:16:43 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 6B7AF7300A; Fri, 17 Jan 2014 00:19:02 +0100 (CET) Date: Fri, 17 Jan 2014 00:19:02 +0100 From: Luigi Rizzo To: current@freebsd.org Subject: picking a new AF_* number for NETLINK ? Message-ID: <20140116231902.GA51955@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) 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: Thu, 16 Jan 2014 23:16:45 -0000 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. cheers luigi