[lkml]   [2015]   [Apr]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v2 01/17] IB/Verbs: Implement new callback query_transport() for each HW
On 04/10/2015 08:16 AM, ira.weiny wrote:
> First off there are 2 separate issues here:
> 1) We need to communicate if a port supports or requires various management
> support from the ib_mad, ib_cm, and/or ib_sa modules.
> 2) We need to communicate how a addresses are formated and resolved for a
> particular port
> In general I don't think we need to remove all uses of the Transport
> or Link Layer.
> Although we may be able to remove most of the transport uses.
> On Wed, Apr 08, 2015 at 02:10:15PM -0600, Jason Gunthorpe wrote:
>> Some of the other checks in this file revolve around pkey, I'm not
>> sure what rocee does there? cap_pkey_supported ?
> It seems IBoE just hardcodes the pkey to 0xffff. I don't see it used anywhere.
> Function where port requires "real" PKey
> -- cma.c: cma_ib_init_qp_attr
> Check rdma_port_req_pkey()?

What about cap_eth_ah() for all the cases need eth addressing handling?

> Over all for the addressing choices:
> The "Transport" (or protocol, or whatever) is Verbs. The Layer below Verbs
> (OPA/IB/Eth/TCP) defines how addressing, route, and connection information is
> generated, communicated, and used.
> As Jason and Doug have been saying sometimes we want to know when that requires
> SA interaction or the use of the CM protocol (or neither). Other times we just
> need to know what the Address format or Link Layer is.

Till now it seems like we could be able to eliminate the link layer helper in core
layer, but I'll reserve that helper in next version, if later we do not need it anymore,
let's erase it then ;-)

Michael Wang

> Ira

 \ /
  Last update: 2015-04-10 11:01    [W:0.209 / U:2.304 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site