On Tue, Sep 13, 2016 at 10:13:10PM +0000, Hefty, Sean wrote: > > The intent is to cover the user space component of the kernel. > > > > So, if code is including uapi/rdma/* then it is a good candidate for > > this tree. > > Based on discussions so far, I would limit the scope to the 'common' > or 'shared' or non-vendor-specific areas of the uAPI. Seems reasonable and on point.. > > libacm, I am unclear on. Is it the recommended userspace component for > > the netlink socket that Kaike? Is it coupled to librdmacm? If yes it > > should probably come too. > > Yes, this is the userspace daemon for the SA netlink socket. And to > be clear, it's ibacm, as it's a daemon not a library. The librdmacm > looks for and uses ibacm when present. Yes/No to include it? Jason -- 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
