> From: Jason Gunthorpe [mailto:jgunthorpe@xxxxxxxxxxxxxxxxxxxx] > > > Anyway, returning to the initial matter at hand: I would like to start > > with each port reporting a bit mask of the supported protocols on that > > link (RoCE v1/v2, Raw Ethernet, iWARP, etc.) It will be used for > > reporting device capabilities in general for tools, as well as by > > applications that don't use rdmacm. > > Why don't we start by defining how it is supposed to even work and how to fix > the RDMA CM before adding even more random capability bits? > > Jason Extensions to RDMA CM is an important topic, which we can continue to discuss as devices that require it are introduced. Protocol capabilities are needed for information purposes as well as for applications that do not use RDMA CM. They are not "random", but depict what a device can do. --Liran -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
