netdev - Re: [PATCH 00/10] Add HA and LAG support to mlx4 RoCE and SRIOV services

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 04 Feb 2015 16:14:50 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	ogerlitz@...lanox.com
Cc:	netdev@...r.kernel.org, roland@...nel.org, amirv@...lanox.com,
	talal@...lanox.com
Subject: Re: [PATCH 00/10] Add HA and LAG support to mlx4 RoCE and SRIOV
 services

From: Or Gerlitz <ogerlitz@...lanox.com>
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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html