From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH 00/10] Add HA and LAG support to mlx4 RoCE and SRIOV services Date: Wed, 04 Feb 2015 16:14:50 -0800 (PST) Message-ID: <20150204.161450.1399793400707389786.davem@davemloft.net> References: <1422974919-28084-1-git-send-email-ogerlitz@mellanox.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, roland@kernel.org, amirv@mellanox.com, talal@mellanox.com To: ogerlitz@mellanox.com Return-path: Received: from shards.monkeyblade.net ([149.20.54.216]:39755 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755967AbbBEAOv (ORCPT ); Wed, 4 Feb 2015 19:14:51 -0500 In-Reply-To: <1422974919-28084-1-git-send-email-ogerlitz@mellanox.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Or Gerlitz Date: Tue, 3 Feb 2015 16:48:28 +0200 > This series takes advanges of bonding mlx4 Ethernet devices to support > a model of High-Availability and Link Aggregation for more environments. > > The mlx4 driver reacts on netdev events generated by bonding when > slave state changes happen by programming a HW V2P (Virt-to-Phys) > port table. Bonding was extended to expose these state changes > through netdev events. > > When an mlx4 interface such as the mlx4 IB/RoCE driver is subject to > this policy, QPs are created over virtual ports which are mapped > to one of the two physical ports. When a failure happens, the > re-programming of the V2P table allows traffic to keep flowing. > > The mlx4 Ethernet driver interfaces are not subject to this > policy and act as usual. > > A 2nd use-case for this model would be to add HA and Link Aggregation > support to single ported mlx4 Ethernet VFs. In this case, the PF Ethernet > intrfaces are bonded, all the VFs see single port devices (which is > supported already today), and VF QPs are subject to V2P. Series applied, thanks.