Hi Doug,
Here are couple OPA_VNIC bug fixes.
As OPA_VNIC is alredy included for 4.12, it would be great
to get them into the RC release.
Thanks,
Niranjana
Vishwanathapura, Niranjana (2):
IB/opa_vnic: Use GFP_ATOMIC while sending trap
IB/opa_vnic: Use spinlock instead of mutex for stats_lock
HFI1 VNIC SDMA support enables transmission of VNIC packets over SDMA.
Map VNIC queues to SDMA engines and support halting and wakeup of the
VNIC queues.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
---
drivers/infiniband/hw/hfi1/Makefile|
Define VNIC EM MAD structures and the associated macros. These structures
are used for information exchange between VNIC EM agent (EMA) on the host
and the Ethernet manager. These include the virtual ethernet switch (vesw)
port information, vesw port mac table, summay and error counters,
vesw port
OPA VNIC driver statistics support maintains various counters including
standard netdev counters and the Ethernet manager defined counters.
Add the Ethtool hook to read the counters.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
---
drivers/inf
Add rdma netdev interface to ib device structure allowing rdma netdev
devices to be allocated by ib clients.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
---
include/rdma/ib_verbs.h | 33 +
1 file changed, 33 in
OPA VNIC netdev function supports Ethernet functionality over Omni-Path
fabric by encapsulating Ethernet packets inside Omni-Path packet header.
It allocates a rdma netdev device and interfaces with the network stack to
provide standard Ethernet network interfaces. It overrides HFI1 device's
netdev
OPA VNIC MAC table contains the MAC address to DLID mappings provided by
the Ethernet manager. During transmission, the MAC table provides the MAC
address to DLID translation. Implement MAC table using simple hash list.
Also provide support to update/query the MAC table by Ethernet manager.
Review
Add support to create and free OPA_VNIC rdma netdev devices.
Implement netstack interface functionality including xmit_skb,
receive side NAPI etc. Also implement rdma netdev control functions.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
Signed
HFI1 HW specific support for VNIC functionality.
Dynamically allocate a set of contexts for VNIC when the first vnic
port is instantiated. Allocate VNIC contexts from user contexts pool
and return them back to the same pool while freeing up. Set aside
enough MSI-X interrupts for VNIC contexts and a
OPA VNIC EMA interface functions are the management interfaces to the OPA
VNIC netdev. Add support to add and remove VNIC ports. Implement the
required GET/SET management interface functions and processing of new
management information. Add support to send trap notifications upon various
events lik
OPA VEMA function interfaces with the Infiniband MAD stack to exchange the
management information packets with the Ethernet Manager (EM).
It interfaces with the OPA VNIC netdev function to SET/GET the management
information. The information exchanged with the EM includes class port
details, encapsu
Add OPA VNIC design document explaining the VNIC architecture and the
driver design.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
---
Documentation/infiniband/opa_vnic.txt | 153 ++
1 file changed, 153 insertion
HFI1 Driver with VNIC support |
||
+--------+
Vishwanathapura, Niranjana (12):
IB/opa-vnic: Virtual Network Interface Controller (VNIC) documentation
IB/opa-vnic: RDMA NETDEV interface
IB/opa-vnic: Virtual Network Interface Controller (VNIC) interface
IB/opa-vnic: Virtual Network Interface Con
Define OPA VNIC interface between hardware independent VNIC
functionality and the hardware dependent VNIC functionality.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
---
include/rdma/ib_verbs.h | 1 +
include/rdma/opa_vnic.h | 141 ++
On Wed, Apr 12, 2017 at 09:56:21AM -0600, Jason Gunthorpe wrote:
On Tue, Apr 11, 2017 at 11:40:05PM -0700, Vishwanathapura, Niranjana wrote:
Add support to create and free OPA_VNIC rdma netdev devices.
Implement netstack interface functionality including xmit_skb,
receive side NAPI etc. Also
On Wed, Apr 12, 2017 at 10:08:30AM +0300, Leon Romanovsky wrote:
+#define v_dbg(format, arg...) \
+ netdev_dbg(adapter->netdev, format, ## arg)
+#define v_err(format, arg...) \
+ netdev_err(adapter->netdev, format, ## arg)
+#define v_info(format, arg...) \
+ netdev_info(adapter-
OPA VNIC netdev function supports Ethernet functionality over Omni-Path
fabric by encapsulating Ethernet packets inside Omni-Path packet header.
It allocates a rdma netdev device and interfaces with the network stack to
provide standard Ethernet network interfaces. It overrides HFI1 device's
netdev
Define VNIC EM MAD structures and the associated macros. These structures
are used for information exchange between VNIC EM agent (EMA) on the host
and the Ethernet manager. These include the virtual ethernet switch (vesw)
port information, vesw port mac table, summay and error counters,
vesw port
Add rdma netdev interface to ib device structure allowing rdma netdev
devices to be allocated by ib clients.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
---
include/rdma/ib_verbs.h | 28
1 file changed, 28 inserti
Add support to create and free OPA_VNIC rdma netdev devices.
Implement netstack interface functionality including xmit_skb,
receive side NAPI etc. Also implement rdma netdev control functions.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
Signed
OPA VNIC EMA interface functions are the management interfaces to the OPA
VNIC netdev. Add support to add and remove VNIC ports. Implement the
required GET/SET management interface functions and processing of new
management information. Add support to send trap notifications upon various
events lik
HFI1 VNIC SDMA support enables transmission of VNIC packets over SDMA.
Map VNIC queues to SDMA engines and support halting and wakeup of the
VNIC queues.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
---
drivers/infiniband/hw/hfi1/Makefile|
Add OPA VNIC design document explaining the VNIC architecture and the
driver design.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
---
Documentation/infiniband/opa_vnic.txt | 153 ++
1 file changed, 153 insertion
HFI1 HW specific support for VNIC functionality.
Dynamically allocate a set of contexts for VNIC when the first vnic
port is instantiated. Allocate VNIC contexts from user contexts pool
and return them back to the same pool while freeing up. Set aside
enough MSI-X interrupts for VNIC contexts and a
OPA VNIC driver statistics support maintains various counters including
standard netdev counters and the Ethernet manager defined counters.
Add the Ethtool hook to read the counters.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
---
drivers/inf
OPA VNIC MAC table contains the MAC address to DLID mappings provided by
the Ethernet manager. During transmission, the MAC table provides the MAC
address to DLID translation. Implement MAC table using simple hash list.
Also provide support to update/query the MAC table by Ethernet manager.
Review
Define OPA VNIC interface between hardware independent VNIC
functionality and the hardware dependent VNIC functionality.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
---
include/rdma/ib_verbs.h | 1 +
include/rdma/opa_vnic.h | 141 ++
|
| HFI1 Driver with VNIC support |
||
+--------+
Vishwanathapura, Niranjana (12):
IB/opa-vnic: Virtual Network Interface Controller (VNIC) documentation
IB/opa-vnic: RDM
OPA VEMA function interfaces with the Infiniband MAD stack to exchange the
management information packets with the Ethernet Manager (EM).
It interfaces with the OPA VNIC netdev function to SET/GET the management
information. The information exchanged with the EM includes class port
details, encapsu
On Wed, Mar 15, 2017 at 08:30:43AM +0200, Leon Romanovsky wrote:
On Tue, Mar 14, 2017 at 10:11:49AM -0600, Jason Gunthorpe wrote:
On Tue, Mar 14, 2017 at 12:01:09AM -0700, Vishwanathapura, Niranjana wrote:
> On Mon, Mar 13, 2017 at 02:01:36PM -0600, Jason Gunthorpe wrote:
> >>+
On Mon, Mar 13, 2017 at 02:01:36PM -0600, Jason Gunthorpe wrote:
+ /* multicast */
+ int (*attach_mcast)(struct net_device *dev, struct ib_device *hca,
+ union ib_gid *gid, u16 lid, int set_qkey);
+ int (*detach_mcast)(struct net_device *dev, struct ib_
On Mon, Mar 13, 2017 at 08:31:15PM +0200, Erez Shitrit wrote:
+struct ipoib_rdma_netdev {
+ struct rdma_netdev rn; /* keep this first */
+ /* followed by device private data */
+ char *dev_priv[0];
+};
+
+static inline void *ipoib_priv(const struct net_device *dev)
+{
+ s
On Mon, Mar 13, 2017 at 08:31:16PM +0200, Erez Shitrit wrote:
+static struct net_device *ipoib_create_netdev_default(struct ib_device *hca,
+ const char *name,
+ void (*setup)(struct
net_devic
On Mon, Mar 13, 2017 at 08:31:36PM +0200, Erez Shitrit wrote:
+int mlx5_ib_dev_init(struct net_device *dev, struct ib_device *hca,
+int *qp_num)
+{
+ void *next_priv = ipoib_dev_priv(dev);
+ struct rdma_netdev *rn = netdev_priv(dev);
+ struct mlx5_ib_dev *ib_
On Wed, Feb 08, 2017 at 05:00:45PM +, Bart Van Assche wrote:
On Tue, 2017-02-07 at 12:23 -0800, Vishwanathapura, Niranjana wrote:
Please elaborate this section. What is a virtual Ethernet switch? Is it a
software entity or something that is implemented in hardware? Also, how are
these
Driver with VNIC support |
||
+--------+
Vishwanathapura, Niranjana (11):
IB/opa-vnic: Virtual Network Interface Controller (VNIC) documentation
IB/opa-vnic: Virtual Network Interface Controller (VNIC) interface
IB/opa-vnic: Virtual Network In
OPA VNIC driver statistics support maintains various counters including
standard netdev counters and the Ethernet manager defined counters.
Add the Ethtool hook to read the counters.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
---
drivers/inf
Define VNIC EM MAD structures and the associated macros. These structures
are used for information exchange between VNIC EM agent (EMA) on the host
and the Ethernet manager. These include the virtual ethernet switch (vesw)
port information, vesw port mac table, summay and error counters,
vesw port
OPA VNIC netdev function supports Ethernet functionality over Omni-Path
fabric by encapsulating Ethernet packets inside Omni-Path packet header.
It allocates a rdma netdev device and interfaces with the network stack to
provide standard Ethernet network interfaces. It overrides HFI1 device's
netdev
Add OPA VNIC design document explaining the VNIC architecture and the
driver design.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
---
Documentation/infiniband/opa_vnic.txt | 153 ++
1 file changed, 153 insertion
HFI1 HW specific support for VNIC functionality.
Dynamically allocate a set of contexts for VNIC when the first vnic
port is instantiated. Allocate VNIC contexts from user contexts pool
and return them back to the same pool while freeing up. Set aside
enough MSI-X interrupts for VNIC contexts and a
OPA VEMA function interfaces with the Infiniband MAD stack to exchange the
management information packets with the Ethernet Manager (EM).
It interfaces with the OPA VNIC netdev function to SET/GET the management
information. The information exchanged with the EM includes class port
details, encapsu
Add rdma netdev interface to ib device structure allowing rdma netdev
devices to be allocated by ib clients.
Define OPA VNIC interface between hardware independent VNIC
functionality and the hardware dependent VNIC functionality.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-
OPA VNIC EMA interface functions are the management interfaces to the OPA
VNIC netdev. Add support to add and remove VNIC ports. Implement the
required GET/SET management interface functions and processing of new
management information. Add support to send trap notifications upon various
events lik
Add support to create and free OPA_VNIC rdma netdev devices.
Implement netstack interface functionality including xmit_skb,
receive side NAPI etc. Also implement rdma netdev control functions.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
Signed
HFI1 VNIC SDMA support enables transmission of VNIC packets over SDMA.
Map VNIC queues to SDMA engines and support halting and wakeup of the
VNIC queues.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
---
drivers/infiniband/hw/hfi1/Makefile|
OPA VNIC MAC table contains the MAC address to DLID mappings provided by
the Ethernet manager. During transmission, the MAC table provides the MAC
address to DLID translation. Implement MAC table using simple hash list.
Also provide support to update/query the MAC table by Ethernet manager.
Review
On Mon, Feb 13, 2017 at 10:09:35AM -0700, Jason Gunthorpe wrote:
On Sun, Feb 12, 2017 at 01:26:35PM +, Liran Liss wrote:
> From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma-
> ow...@vger.kernel.org] On Behalf Of Vishwanathapura, Niranjana
>
> ChangeLog:
> =
On Wed, Feb 08, 2017 at 04:06:40AM +, Parav Pandit wrote:
Hi,
-Original Message-
From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma-
ow...@vger.kernel.org] On Behalf Of Vishwanathapura, Niranjana
Sent: Tuesday, February 7, 2017 2:23 PM
To: dledf...@redhat.com
Cc: linux-r
On Wed, Feb 08, 2017 at 12:43:40AM +, Parav Pandit wrote:
@@ -2096,6 +2114,15 @@ struct ib_device {
struct
ib_rwq_ind_table_init_attr *init_attr,
struct ib_udata
*udata);
On Tue, Feb 07, 2017 at 03:19:25PM -0700, Jason Gunthorpe wrote:
On Tue, Feb 07, 2017 at 02:06:30PM -0800, Vishwanathapura, Niranjana wrote:
>>IB_DEVICE_RAW_SCATTER_FCS = (1ULL << 34),
>>+ IB_DEVICE_RDMA_NETDEV_HFI_VNIC = (1ULL <&
On Tue, Feb 07, 2017 at 09:58:50PM +, Bart Van Assche wrote:
On Tue, 2017-02-07 at 21:44 +, Hefty, Sean wrote:
This is Ethernet - not IP - encapsulation over a non-InfiniBand device/protocol.
That's more than clear from the cover letter. In my opinion the cover letter
should explain wh
On Tue, Feb 07, 2017 at 02:19:01PM -0700, Jason Gunthorpe wrote:
On Tue, Feb 07, 2017 at 12:23:01PM -0800, Vishwanathapura, Niranjana wrote:
Add rdma netdev interface to ib device structure allowing rdma netdev
devices to be allocated by ib clients.
Define HFI VNIC interface between hardware
On Tue, Feb 07, 2017 at 01:00:05PM -0800, Hefty, Sean wrote:
I didn't read patches yet, and prefer to ask it in advance. Does this
new ULP work with all
drivers/infiniband/hw/* devices as it is expected from ULP?
Like the way ipoib or srp work with all hw devices? What is the real point of
th
Define VNIC EM MAD structures and the associated macros. These structures
are used for information exchange between VNIC EM agent (EMA) on the HFI
host and the Ethernet manager. These include the virtual ethernet switch
(vesw) port information, vesw port mac table, summay and error counters,
vesw p
HFI VNIC netdev function supports Ethernet functionality over Omni-Path
fabric by encapsulating Ethernet packets inside Omni-Path packet header.
It allocates a rdma netdev device and interfaces with the network stack to
provide standard Ethernet network interfaces. It overrides HFI device's
netdev
HFI1 HW specific support for VNIC functionality.
Dynamically allocate a set of contexts for VNIC when the first vnic
port is instantiated. Allocate VNIC contexts from user contexts pool
and return them back to the same pool while freeing up. Set aside
enough MSI-X interrupts for VNIC contexts and a
HFI1 VNIC SDMA support enables transmission of VNIC packets over SDMA.
Map VNIC queues to SDMA engines and support halting and wakeup of the
VNIC queues.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
---
drivers/infiniband/hw/hfi1/Makefile|
Add support to create and free HFI_VNIC rdma netdev devices.
Implement netstack interface functionality including xmit_skb,
receive side NAPI etc. Also implement rdma netdev control functions.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
Signed
HFI VNIC EMA interface functions are the management interfaces to the HFI
VNIC netdev. Add support to add and remove VNIC ports. Implement the
required GET/SET management interface functions and processing of new
management information. Add support to send trap notifications upon various
events lik
HFI VNIC MAC table contains the MAC address to DLID mappings provided by
the Ethernet manager. During transmission, the MAC table provides the MAC
address to DLID translation. Implement MAC table using simple hash list.
Also provide support to update/query the MAC table by Ethernet manager.
Review
HFI VNIC driver statistics support maintains various counters including
standard netdev counters and the Ethernet manager defined counters.
Add the Ethtool hook to read the counters.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
---
drivers/inf
HFI VEMA function interfaces with the Infiniband MAD stack to exchange the
management information packets with the Ethernet Manager (EM).
It interfaces with the HFI VNIC netdev function to SET/GET the management
information. The information exchanged with the EM includes class port
details, encapsu
Add rdma netdev interface to ib device structure allowing rdma netdev
devices to be allocated by ib clients.
Define HFI VNIC interface between hardware independent VNIC
functionality and the hardware dependent VNIC functionality.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-
Add HFI VNIC design document explaining the VNIC architecture and the
driver design.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
---
Documentation/infiniband/hfi_vnic.txt | 102 ++
1 file changed, 102 insertion
support |
||
++
Vishwanathapura, Niranjana (11):
IB/hfi-vnic: Virtual Network Interface Controller (VNIC) documentation
IB/hfi-vnic: Virtual Network Interface Controller (VNIC) interface
IB/hfi-vnic: Virtual Network Interface Controller (VNIC) netdev
IB/hfi-vnic: VNIC Ethernet Managem
Thanks Jason for the valuable inputs.
Here is the new generic interface.
Overview:
Bottom driver defines net_device_ops. The upper driver can override it.
For example, upper driver can implement ndo_open() which calls bottom driver's
ndo_open() and also do some book keeping.
include/rdma/ib_
On Tue, Jan 10, 2017 at 10:14:02AM +0200, Leon Romanovsky wrote:
On Mon, Jan 09, 2017 at 07:39:54PM -0800, Vishwanathapura, Niranjana wrote:
We are also looking into Jason’s suggestion to make hfi_vnic interface to
the bottom driver a generic interface. This will include moving some of the
On Mon, Jan 09, 2017 at 09:51:04AM +0200, Leon Romanovsky wrote:
On Thu, Dec 15, 2016 at 11:28:06AM -0500, Doug Ledford wrote:
On 12/15/2016 9:52 AM, ira.weiny wrote:
2) With more than 60% of the code being MAD related, and another
significant chunk being hfi related, and only a minor bit (20%
On Thu, Dec 15, 2016 at 09:24:20PM -0700, Jason Gunthorpe wrote:
>>+struct __hfi_vesw_info {
>>+ u16 fabric_id;
>>+ u16 vesw_id;
>>+
>>+ u8 rsvd0[6];
>>+ u16 def_port_mask;
>>+
>>+ u8 rsvd1[2];
>>+ u16 pkey;
>>+
>>+ u8 rsvd2[4];
>>+ u32 u
On Thu, Dec 15, 2016 at 09:56:11AM -0700, Jason Gunthorpe wrote:
On Wed, Dec 14, 2016 at 11:59:32PM -0800, Vishwanathapura, Niranjana wrote:
create mode 100644 drivers/infiniband/sw/intel/hfi_vnic/Kconfig
create mode 100644 drivers/infiniband/sw/intel/hfi_vnic/Makefile
Stil NAK on these
On Thu, Dec 15, 2016 at 10:01:09AM -0700, Jason Gunthorpe wrote:
On Wed, Dec 14, 2016 at 11:59:35PM -0800, Vishwanathapura, Niranjana wrote:
+/**
+ * union hfi_vnic_bypass_hdr - VNIC bypass header
+ * @slid: source lid
+ * @length: length of packet
+ * @becn: backward explicit congestion
On Thu, Dec 15, 2016 at 10:07:13AM -0700, Jason Gunthorpe wrote:
On Thu, Dec 15, 2016 at 11:28:06AM -0500, Doug Ledford wrote:
1) Since your intent is to make this work with multiple versions of the
hfi drivers, I disagree with Jason that just because there is only one
driver today that we shou
On Thu, Dec 15, 2016 at 08:24:05PM -0500, ira.weiny wrote:
On Thu, Dec 15, 2016 at 11:48:37AM -0700, Jason Gunthorpe wrote:
On Thu, Dec 15, 2016 at 01:19:18PM -0500, Doug Ledford wrote:
> On 12/15/2016 12:07 PM, Jason Gunthorpe wrote:
> > On Thu, Dec 15, 2016 at 11:28:06AM -0500, Doug Ledford wr
On Wed, Dec 14, 2016 at 11:59:34PM -0800, Vishwanathapura, Niranjana wrote:
+
+static inline bool is_hfi_ibdev(struct ib_device *ibdev)
+{
+ return !memcmp(ibdev->name, "hfi", 3);
+}
I am thinking of adding a device capability flag to indicate HFI VNIC capabilty
instead
HFI VEMA function interfaces with the Infiniband MAD stack to exchange the
management information packets with the Ethernet Manager (EM).
It interfaces with the HFI VNIC netdev function to SET/GET the management
information. The information exchanged with the EM includes class port
details, encapsu
HFI VNIC driver statistics support maintains various counters including
standard netdev counters and the Ethernet manager defined counters.
Add the Ethtool hook to read the counters.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
---
.../infinib
HFI1 HW specific support for VNIC functionality. Add support to add
and remove VNIC ports. Also implement the operations to allocate
resources, transmit and receive of Omni-Path encapsulated Ethernet
packets.
Dynamically allocate a set of contexts for VNIC when the first vnic
port is instantiated.
HFI1 VNIC SDMA support enables transmission of VNIC packets over SDMA.
Map VNIC queues to SDMA engines and support halting and wakeup of the
VNIC queues.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
---
drivers/infiniband/hw/hfi1/hfi.h |
Add HFI VNIC design document explaining the VNIC architecture and the
driver design.
Reviewed-by: Dennis Dalessandro
Reviewed-by: Ira Weiny
Signed-off-by: Niranjana Vishwanathapura
---
Documentation/infiniband/hfi_vnic.txt | 95 +++
1 file changed, 95 insertions
Define VNIC EM MAD structures and the associated macros. These structures
are used for information exchange between VNIC EM agent (EMA) on the HFI
host and the Ethernet manager. These include the virtual ethernet switch
(vesw) port information, vesw port mac table, summay and error counters,
vesw p
with VNIC support |
||
+----+
Vishwanathapura, Niranjana (10):
IB/hfi-vnic: Virtual Network Interface Controller (VNIC) documentation
IB/hfi-vnic: Virtual Network Interface Controller (VNIC) interface
IB/hfi-vnic: Virtual Network Interface Controller (VNIC) netdev
HFI VNIC MAC table contains the MAC address to DLID mappings provided by
the Ethernet manager. During transmission, the MAC table provides the MAC
address to DLID translation. Implement MAC table using simple hash list.
Also provide support to update/query the MAC table by Ethernet manager.
Review
HFI VNIC EMA interface functions are the management interfaces to the HFI
VNIC netdev. Add support to add and remove VNIC ports. Implement the
required GET/SET management interface functions and processing of new
management information. Add support to send trap notifications upon various
events lik
Create hfi_ibdev abstraction which hfi1_ibdev will extend.
Define HFI VNIC interface between hardware independent VNIC
functionality and the hardware dependent VNIC functionality.
Add VNIC control operations to add and remove VNIC devices,
to the hfi_ibdev structure.
Reviewed-by: Dennis Dalessandr
HFI VNIC netdev function supports Ethernet functionality over Omni-Path
fabric by encapsulating Ethernet packets inside Omni-Path packet header.
It interfaces with the network stack to provide standard Ethernet network
interfaces. It invokes HFI device's VNIC callback functions for HW access.
Revi
On Tue, Nov 29, 2016 at 09:21:13AM -0700, Jason Gunthorpe wrote:
On Mon, Nov 28, 2016 at 10:29:38PM -0800, Vishwanathapura, Niranjana wrote:
On Thu, Nov 24, 2016 at 09:15:45AM -0700, Jason Gunthorpe wrote:
>>And will move the hfi_vnic module under
>>???drivers/infiniband/ulp/hfi_v
On Tue, Nov 29, 2016 at 09:50:09AM -0700, Jason Gunthorpe wrote:
On Tue, Nov 29, 2016 at 04:44:37PM +, Hefty, Sean wrote:
> You are not making a subsystem. Don't overcomplicate things. A
> multi-part device device can just directly link.
The VNIC may be usable over multiple generations of H
On Fri, Nov 25, 2016 at 12:05:09PM -0700, Jason Gunthorpe wrote:
On Thu, Nov 24, 2016 at 06:13:50PM -0800, Vishwanathapura, Niranjana wrote:
In order to be truely device independent the hfi_vnic ULP should not depend
on a device exported symbol. Instead device should register its functions
On Thu, Nov 24, 2016 at 09:15:45AM -0700, Jason Gunthorpe wrote:
And will move the hfi_vnic module under
‘drivers/infiniband/ulp/hfi_vnic’.
I would prefer drivers/net/ethernet
This is clearly not a ULP since it doesn't use verbs.
I understand it is not using verbs, but the control path (ib_
On Thu, Nov 24, 2016 at 09:15:45AM -0700, Jason Gunthorpe wrote:
On Wed, Nov 23, 2016 at 04:08:25PM -0800, Vishwanathapura, Niranjana wrote:
In order to pass the hfi function pointers to the hfi_vnic ULP, I can,
a) Have hfi_vnic ULP define an interface API for hfi1 driver to call to
register
On Tue, Nov 22, 2016 at 05:49:32PM -0700, Jason Gunthorpe wrote:
> > We could add a custom Interface between HFI1 driver and hfi_vnic drivers
> > without involving a bus.
>
> hfi is already registering on the infiniband class, just use that.
I don't understand what you mean here?
Get the struc
On Tue, Nov 22, 2016 at 05:04:37PM -0600, Christoph Lameter wrote:
On Tue, 22 Nov 2016, Vishwanathapura, Niranjana wrote:
Ok, I do understand Jason's point that we should probably not put this driver
under drivers/infiniband/sw/.., as this driver is not a HCA.
It is an ULP similar to
Ok, I do understand Jason's point that we should probably not put this driver
under drivers/infiniband/sw/.., as this driver is not a HCA.
It is an ULP similar to ipoib, built on top of Omni-path irrespective of
whether we register a hfi_vnic_bus or a direct custom interface with HFI1.
This ULP w
On Mon, Nov 21, 2016 at 04:31:18PM -0700, Jason Gunthorpe wrote:
+ ida_init(&hfi_vnic_ctrl_ida);
+ idr_init(&hfi_vnic_idr);
+
+ rc = bus_register(&hfi_vnic_bus);
>>>
>>>Why on earth do we need this? Didn't I give you enough grief for the
>>>psm stuff and now you
On Mon, Nov 21, 2016 at 02:39:30PM -0700, Jason Gunthorpe wrote:
On Mon, Nov 21, 2016 at 01:30:17PM -0800, Vishwanathapura, Niranjana wrote:
On Sat, Nov 19, 2016 at 12:04:45PM -0700, Jason Gunthorpe wrote:
>On Fri, Nov 18, 2016 at 02:42:10PM -0800, Vishwanathapura, Niranjana wrote:
>>
On Sat, Nov 19, 2016 at 12:04:45PM -0700, Jason Gunthorpe wrote:
On Fri, Nov 18, 2016 at 02:42:10PM -0800, Vishwanathapura, Niranjana wrote:
+HFI-VNIC DRIVER
+M: Dennis Dalessandro
+M: Niranjana Vishwanathapura
+L: linux-r...@vger.kernel.org
+S: Supported
+F: drivers
HFI1 VNIC SDMA support enables transmission of VNIC packets over SDMA.
Map VNIC queues to SDMA engines and support halting and wakeup of the
VNIC queues.
Change-Id: I2d2d23bda9fb8a7194d9722e23bc69b110cdcf86
Reviewed-by: Dennis Dalessandro
Signed-off-by: Niranjana Vishwanathapura
---
drivers/inf
HFI VEMA driver interfaces with the Infiniband MAD stack to exchange the
management information packets with the Ethernet Manager (EM).
It interfaces with the HFI VNIC netdev driver to SET/GET the management
information. The information exchanged with the EM includes class port
details, encapsulati
HFI1 HW specific support for VNIC functionality. Add support to create
VNIC devices on HFI VNIC Bus. Also implement the bus operations to
allocate resources, transmit and receive of Omni-Path encapsulated
Ethernet packets.
Dynamically allocate a set of contexts for VNIC when the first vnic
port is
1 - 100 of 108 matches
Mail list logo
