From owner-freebsd-current@FreeBSD.ORG  Fri Jan 17 16:10:55 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 7AB52C2C;
 Fri, 17 Jan 2014 16:10:55 +0000 (UTC)
Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com
 [IPv6:2a00:1450:4010:c04::22a])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id C4EE311DE;
 Fri, 17 Jan 2014 16:10:54 +0000 (UTC)
Received: by mail-lb0-f170.google.com with SMTP id u14so3171785lbd.1
 for <multiple recipients>; Fri, 17 Jan 2014 08:10:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date:message-id:subject
 :from:to:cc:content-type;
 bh=j1K7/t6rf/QexbM53/lJHbvIpKdvEPKtzosvLQOhNog=;
 b=D+kH3A8ScSa8Oipf8VbMKlVdQ8IwsFtBxAUhnFoIiMsDINt4cPvXfj9ZD0hC9dO6H5
 tlJOAoaw8arH6UsGhMLJExSfvzl51ZzML9dY7mNWD1vvN4iQlJRoNnAx6LHCEdXchIY6
 dF//uzENa8M/Iu94GUvhtFM3nRCOy8izmUUUNoN+O4TQIKUIa4e43qidgo5tTYhEsITO
 WTLevns0RFF4QY9wOX42GOV1DslnOKUVy9WCnoEgr7k3VlyRXhdu/4t+3FuEArnDs41V
 Kdd5GLjB+yqjv1Crztuch+PW8IcELwE8a5eNq/plWCpqGQSJeJLYPNoakkYbYpu5hx9W
 vbmw==
MIME-Version: 1.0
X-Received: by 10.152.180.35 with SMTP id dl3mr637508lac.66.1389975052739;
 Fri, 17 Jan 2014 08:10:52 -0800 (PST)
Sender: rizzo.unipi@gmail.com
Received: by 10.114.175.180 with HTTP; Fri, 17 Jan 2014 08:10:52 -0800 (PST)
In-Reply-To: <52D95305.6020909@FreeBSD.org>
References: <20140116231902.GA51955@onelab2.iet.unipi.it>
 <52D95305.6020909@FreeBSD.org>
Date: Fri, 17 Jan 2014 08:10:52 -0800
X-Google-Sender-Auth: 4qynfCVqhWPlTk7kh92bg4D7EHc
Message-ID: <CA+hQ2+iPSxdb3166Cvx+e7PABds=qg-37yeTzpvmQE-rv+N5eg@mail.gmail.com>
Subject: Re: picking a new AF_* number for NETLINK ?
From: Luigi Rizzo <rizzo@iet.unipi.it>
To: "Alexander V. Chernikov" <melifaro@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.17
Cc: FreeBSD Current <current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2014 16:10:55 -0000

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