On 12/17/2014 4:28 AM, Alex Netes wrote:
Torus-2QoS fails to configure fabric with more than 16 HCAs.
This patch extends PORTGRP_MAX_PORTS to be 34. Maximal practical ports
per switch - 2 reserved ports (minimal of needed ports for switch to
switch connections in 2D Torus).
Signed-off-by:
Hi Or,
We have some trouble in the past about IPoIB support about neighbour
discovery, AF_IB doesn't relay on IPoIB, so
we think have another option maybe give us more safe in some cases.
On Wed, Dec 17, 2014 at 11:40 AM, Or Gerlitz ogerl...@mellanox.com wrote:
On 12/16/2014 5:43 PM, Jack
The MLX4_PROT_IB_IPV4 protocol should only be used with RoCEv2 and such.
Removing this wrong usage allows to run multicast applications over RoCE.
Fixes: d487ee77740c ('IB/mlx4: Use IBoE (RoCE) IP based GIDs in the port GID
table')
Reported-by: Carol Soto cls...@linux.vnet.ibm.com
Signed-off-by:
Currently, if there is any user space application using an IB device,
it is impossible to unload the HW device driver for this device.
Similarly, if the device is hot-unplugged or reset, the device driver
hardware removal flow blocks until all user contexts are destroyed.
This patchset removes
Enables the uverbs_remove_one to succeed despite the fact that there are
running IB applications working with the given ib device. This functionality
enables a HW device to be unbind/reset despite the fact that there are running
user space applications using it.
It exposes a new IB kernel API
Currently, IB/cma remove_one flow blocks until all user descriptor managed by
IB/ucma are released. This prevents hot-removal of IB devices. This patch
allows IB/cma to remove devices regardless of user space activity. Upon getting
the RDMA_CM_EVENT_DEVICE_REMOVAL event we close all the underlying
Implements the IB core disassociate_ucontext API. The driver detaches the HW
resources for a given user context to prevent a dependency between application
termination and device disconnecting. This is done by managing the VMAs that
were mapped to the HW bars such as door bell and blueflame. When
There is a new 1.3.10.1 release of libibumad.
Tarball is available in:
http://www.openfabrics.org/downloads/management/
(listed in http://www.openfabrics.org/downloads/management/latest.txt)
md5sum:
2fa06c98f025f2153621d66b16203405 libibumad-1.3.10.1.tar.gz
All component versions are from
