From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Pirko Subject: Re: [PATCH net-next v11 3/5] net: Introduce net_failover driver Date: Tue, 22 May 2018 10:59:40 +0200 Message-ID: <20180522085940.GD2149@nanopsycho> References: <1526954781-35359-1-git-send-email-sridhar.samudrala@intel.com> <1526954781-35359-4-git-send-email-sridhar.samudrala@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: mst@redhat.com, stephen@networkplumber.org, davem@davemloft.net, netdev@vger.kernel.org, virtualization@lists.linux-foundation.org, virtio-dev@lists.oasis-open.org, jesse.brandeburg@intel.com, alexander.h.duyck@intel.com, kubakici@wp.pl, jasowang@redhat.com, loseweigh@gmail.com, aaron.f.brown@intel.com, anjali.singhai@intel.com To: Sridhar Samudrala Return-path: Received: from mail-wr0-f195.google.com ([209.85.128.195]:43151 "EHLO mail-wr0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750707AbeEVI7t (ORCPT ); Tue, 22 May 2018 04:59:49 -0400 Received: by mail-wr0-f195.google.com with SMTP id r13-v6so6348106wrj.10 for ; Tue, 22 May 2018 01:59:48 -0700 (PDT) Content-Disposition: inline In-Reply-To: <1526954781-35359-4-git-send-email-sridhar.samudrala@intel.com> Sender: netdev-owner@vger.kernel.org List-ID: Tue, May 22, 2018 at 04:06:19AM CEST, sridhar.samudrala@intel.com wrote: >The net_failover driver provides an automated failover mechanism via APIs >to create and destroy a failover master netdev and mananges a primary and >standby slave netdevs that get registered via the generic failover >infrastructure. > >The failover netdev acts a master device and controls 2 slave devices. The >original paravirtual interface gets registered as 'standby' slave netdev and >a passthru/vf device with the same MAC gets registered as 'primary' slave >netdev. Both 'standby' and 'failover' netdevs are associated with the same >'pci' device. The user accesses the network interface via 'failover' netdev. >The 'failover' netdev chooses 'primary' netdev as default for transmits when >it is available with link up and running. > >This can be used by paravirtual drivers to enable an alternate low latency >datapath. It also enables hypervisor controlled live migration of a VM with >direct attached VF by failing over to the paravirtual datapath when the VF >is unplugged. > >Signed-off-by: Sridhar Samudrala [...] >+ >+The net_failover driver provides an automated failover mechanism via APIs >+to create and destroy a failover master netdev and mananges a primary and s/mananges/manages/