On Thu, Jan 21, 2016 at 07:05:48PM +0200, Or Gerlitz wrote: > On 1/21/2016 5:32 PM, Steve Wise wrote: > >Only a single user-space daemon is used. > > Good. > > >Someone from Intel might have insight into the architecture and design. Perhaps the intention is that individual drivers might want to have their own handlers for these various operations. But currently they all use the core/common ones. > > But if there's single daemon there and one set of pre-defined callbacks, > why different netlink commands are needed? in what case the damon uses > RDMA_NL_NES or RDMA_NL_C4IW or the new define and why? > > Or. The Intel X722 iWARP driver implements the port mapper interface as is in the current kernel, utilizing iwpm. The portmapper daemon sends netlink messages to the client drivers (nes, cxgb4) and RDMA_NL_NES/RDMA_NL_C4IW enums are part of the netlink message header used by the netlink protocol to deliver the messages to the corresponding client. We can certainly take up the discussion on improving the current port mapper design/implementation. But that would be more appropriate in a separate thread. Thanks Faisal -- 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
