[PATCH rdma-next v1 08/13] IB/core: Add support for flow counters

From: Raed Salem A counters object could be attached to flow on creation by providing the counter specification action. General counters description which count packets and bytes are introduced, downstream patches from this series will use them as part of flow counters

[PATCH rdma-next v1 12/13] IB/mlx5: Add flow counters read support

From: Raed Salem Implements the flow counters read wrapper. Reviewed-by: Yishai Hadas Signed-off-by: Raed Salem Signed-off-by: Leon Romanovsky --- drivers/infiniband/hw/mlx5/main.c| 16

[PATCH mlx5-next v1 02/13] net/mlx5: Export flow counter related API

From: Raed Salem Exports counters API to be used in both IB and EN. Reviewed-by: Yishai Hadas Signed-off-by: Raed Salem Signed-off-by: Leon Romanovsky --- drivers/net/ethernet/mellanox/mlx5/core/fs_core.h |

[PATCH rdma-next v1 05/13] IB/core: Introduce counters read verb

From: Raed Salem The user supplies counters instance and a reference to an output array of uint64_t. The driver reads the hardware counters values and writes them to the output index location in the user supplied array. All counters values are represented as uint64_t types.

[PATCH rdma-next v1 13/13] IB/mlx5: Add counters read support

From: Raed Salem This patch implements the uverbs counters read API, it will use the specific read counters function to the given type to accomplish its task. Reviewed-by: Yishai Hadas Signed-off-by: Raed Salem Signed-off-by: Leon

[PATCH rdma-next v1 10/13] IB/mlx5: Add counters create and destroy support

From: Raed Salem This patch implements the device counters create and destroy APIs and introducing some internal management structures. Downstream patches in this series will add the functionality to support flow counters binding and reading. Reviewed-by: Yishai Hadas

[PATCH rdma-next v1 01/13] IB/uverbs: Add an ib_uobject getter to ioctl() infrastructure

From: Matan Barak Previously, the user had to dig inside the attribute to get the uobject. Add a helper function that correctly extract it (and do the required checks) for him/her. Signed-off-by: Matan Barak Signed-off-by: Leon Romanovsky

[PATCH rdma-next v1 00/13] Verbs flow counters support

From: Leon Romanovsky Changelog v0->v1: * Decouple from DevX submission * Use uverbs_attr_get_obj at counters read method * Added define for max read buffer size (MAX_COUNTERS_BUFF_SIZE) * Removed the struct mlx5_ib_flow_counter basic_flow_cnts and the related structs

[PATCH rdma-next v1 06/13] IB/uverbs: Add read counters support

From: Raed Salem This patch exposes the read counters verb to user space applications. By that verb the user can read the hardware counters which are associated with the counters object. The application needs to provide a sufficient memory to hold the statistics.

[PATCH rdma-next v1 03/13] IB/core: Introduce counters object and its create/destroy

From: Raed Salem A verbs application may need to get statistics and info on various aspects of a verb object (e.g. Flow, QP, ...), in general case the application will state which object's counters its interested in (we refer to this action as attach), bind this new counters

[PATCH rdma-next v1 11/13] IB/mlx5: Add flow counters binding support

From: Raed Salem Associates a counters with a flow when IB_FLOW_SPEC_ACTION_COUNT is part of the flow specifications. The counters user space placements of location and description (index, description) pairs are passed as private data of the counters flow specification.

[PATCH rdma-next v1 07/13] IB/core: Support passing uhw for create_flow

From: Matan Barak This is required when user-space drivers need to pass extra information regarding how to handle this flow steering specification. Reviewed-by: Yishai Hadas Signed-off-by: Matan Barak Signed-off-by: Boris

[PATCH rdma-next v1 09/13] IB/uverbs: Add support for flow counters

From: Raed Salem The struct ib_uverbs_flow_spec_action_count associates a counters object with the flow. Post this association the flow counters can be read via the counters object. Reviewed-by: Yishai Hadas Signed-off-by: Raed Salem

[PATCH rdma-next v1 04/13] IB/uverbs: Add create/destroy counters support

From: Raed Salem User space application which uses counters functionality, is expected to allocate/release the counters resources by calling create/destroy verbs and in turn get a unique handle that can be used to attach the counters to its counted type. Reviewed-by: Yishai

Re: [PATCH net] sctp: not allow to set rto_min with a value below 200 msecs

> On 26. May 2018, at 17:50, Dmitry Vyukov wrote: > > On Sat, May 26, 2018 at 5:42 PM, Michael Tuexen > wrote: >>> On 25. May 2018, at 21:13, Neil Horman wrote: >>> >>> On Sat, May 26, 2018 at 01:41:02AM +0800, Xin

[PATCH net-next 1/3] mlxsw: reg: Add Management Reset and Shutdown Register

From: Jiri Pirko Signed-off-by: Jiri Pirko Signed-off-by: Ido Schimmel --- drivers/net/ethernet/mellanox/mlxsw/reg.h | 25 + 1 file changed, 25 insertions(+) diff --git

[PATCH net-next 3/3] mlxsw: pci: Utilize MRSR register to perform FW reset

From: Jiri Pirko So far, the PCI BAR0 register is used for triggering FW reset. However, that is a legacy attitude and it is recommended to use MRSR to perform reset instead. So do that. Move the reset into init() function as the cmd interface needs to be used. With that, IRQ

[PATCH net-next 0/3] mlxsw: use MRSR register for FW reset

Jiri says: Introduce a MRSR register definition and use it to do FW reset instead of existing mechanism using PCI BAR0 register. Jiri Pirko (3): mlxsw: reg: Add Management Reset and Shutdown Register mlxsw: cmd: Handle error after reset gracefully mlxsw: pci: Utilize MRSR register to

[PATCH net-next 2/3] mlxsw: cmd: Handle error after reset gracefully

From: Jiri Pirko There is an exception in command interface processing in case the MRSR register is written to. The register triggers FW reset and during the reset FW returns an error. So handle this by ignoring this error while writing to MRSR register. Signed-off-by: Jiri

[PATCH net] mlxsw: spectrum: Forbid creation of VLAN 1 over port/LAG

From: Petr Machata VLAN 1 is internally used for untagged traffic. Prevent creation of explicit netdevice for that VLAN, because that currently isn't supported and leads to the NULL pointer dereference cited below. Fix by preventing creation of VLAN devices with VID of 1

<    1   2