From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH v2 net-next 0/7] net: l3mdev: Support for sockets bound to enslaved device Date: Sun, 06 Aug 2017 21:39:38 -0700 (PDT) Message-ID: <20170806.213938.1049251959507174455.davem@davemloft.net> References: <1501877823-31365-1-git-send-email-dsahern@gmail.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: dsahern@gmail.com Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:50604 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751366AbdHGEjj (ORCPT ); Mon, 7 Aug 2017 00:39:39 -0400 In-Reply-To: <1501877823-31365-1-git-send-email-dsahern@gmail.com> Sender: netdev-owner@vger.kernel.org List-ID: From: David Ahern Date: Fri, 4 Aug 2017 13:16:56 -0700 > A missing piece to the VRF puzzle is the ability to bind sockets to > devices enslaved to a VRF. This patch set adds the enslaved device > index, sdif, to IPv4 and IPv6 socket lookups. The end result for users > is the following scope options for services: > > 1. "global" services - sockets not bound to any device > > Allows 1 service to work across all network interfaces with > connected sockets bound to the VRF the connection originates > (Requires net.ipv4.tcp_l3mdev_accept=1 for TCP and > net.ipv4.udp_l3mdev_accept=1 for UDP) > > 2. "VRF" local services - sockets bound to a VRF > > Sockets work across all network interfaces enslaved to a VRF but > are limited to just the one VRF. > > 3. "device" services - sockets bound to a specific network interface > > Service works only through the one specific interface. > > v2 > - remove sk_lookup struct and add sdif as an argument to existing > functions > > Changes since RFC: > - no significant logic changes; mainly whitespace cleanups Series applied, thanks David.