On Wed, Oct 02, 2019 at 01:51:00PM -0300, Jason Gunthorpe wrote: > On Wed, Oct 02, 2019 at 08:21:45AM -0700, Bart Van Assche wrote: > > On 10/2/19 7:14 AM, Jason Gunthorpe wrote: > > > On Mon, Sep 30, 2019 at 04:17:01PM -0700, Bart Van Assche wrote: > > >> Management datagrams (MADs) are not supported by SR-IOV VFs nor by > > >> iWARP > > > > > > Really? This seems surprising to me.. > > > > Hi Jason, > > > > Last time I checked the Mellanox drivers allow MADs to be sent over a > > SR-IOV VF but do not allow MADs to be received through such a VF. > > I think that is only true of mlx4, mlx5 allows receive, AFAIK > > I don't know if registering a mad agent fails though. Jack? According to internal mlx5 specification, MAD is fully operational for every Virtual HCA used to connect such virtual devices to IBTA virtualization spec. "Each PCI function (PF or VF) represents a vHCA. Each vHCA virtual port is mapped to an InfiniBand vport. The mapping is arbitrary and determined by the device, as the InfiniBand management is agnostic to it (the InfiniBand specification has no notion of hosts or PCI functions)." Most probably the observed by Bart behaviour is related to the fact that vport0 has special meaning to allow legacy SMs to connect. Thanks > > > I haven't been able to find any reference to management datagrams in the > > iWARP RFC. Maybe that means that I overlooked something? > > Iwarp makes sense > > Jason
