[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1432210450-23408-1-git-send-email-ogerlitz@mellanox.com>
Date: Thu, 21 May 2015 15:14:04 +0300
From: Or Gerlitz <ogerlitz@...lanox.com>
To: "David S. Miller" <davem@...emloft.net>
Cc: netdev@...r.kernel.org, Matan Barak <matanb@...lanox.com>,
Doug Ledford <dledford@...hat.com>,
Amir Vadai <amirv@...lanox.com>, Tal Alon <talal@...lanox.com>,
Jack Morgenstein <jackm@....mellanox.co.il>,
Or Gerlitz <ogerlitz@...lanox.com>
Subject: [PATCH net-next 0/6] mlx4: Enable single ported VFs over IB ports
Hi Dave,
This series further enhances the support for mlx4 single ported VFs
introduced in 3.15 to work over IB ports too.
Just as quick reminder, the ConnectX3 device family exposes one PCI device
which serves both ports.
This can be non-optimal under virtualization schemes where the admin
would like the VF to expose one interface to the VM, etc.
Since all the VF interaction with the firmware passes through the PF
driver, we can emulate to the VF they have one port, and further create
a set of the VFs which act on port1 of the device and another set which
acts on port2.
Or.
Or Gerlitz (6):
net/mlx4_core: Enhance the MAD_IFC wrapper to convert VF port to physical
IB/mlx4: Convert slave port before building address-handle
net/mlx4_core: Modify port values when generting EQEs for VFs
net/mlx4_core: Adjust the schedule queue port for single ported IB VFs
net/mlx4_core: Adjust the schedule queue port in reset-to-init too
net/mlx4_core: Enable single ported IB VFs
drivers/infiniband/hw/mlx4/alias_GUID.c | 7 +++++-
drivers/infiniband/hw/mlx4/mad.c | 11 +++++---
drivers/net/ethernet/mellanox/mlx4/cmd.c | 21 ++++++++++++++---
drivers/net/ethernet/mellanox/mlx4/eq.c | 24 ++++++++++++++++---
drivers/net/ethernet/mellanox/mlx4/main.c | 12 ----------
.../net/ethernet/mellanox/mlx4/resource_tracker.c | 12 ++++++++-
6 files changed, 60 insertions(+), 27 deletions(-)
--
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
Powered by blists - more mailing lists