> From: Jason Gunthorpe <jguntho...@obsidianresearch.com> > > >fill mr->key by the lkey or rkey based on that and everything will > > >work fine. > > > > But the ULP *can* register a memory buffer with local and remote > > access permissions. > Not in the new API. > > If a ULP ever comes along that does need that then they can start with > two MRs and then eventually upgrade the kapi to have some kind of > efficient bidir MR mode.
ULPs are *already* using the same registrations for both local and remote access. So, currently, this is a no-go. Sorry. Let's make the required adjustments, which don't violate specs, and then continue. > > What we've seen on the list lately is that every single ULP seems to > have technical problems running the stack properly. We need to get off > this idea that the spec has to govern the kapi - that didn't lead us > any place nice. > Oh, please. Our stack connects millions of endpoints in production using multiple ULPs for the last 15 years with full interoperability because of specs. I am sure that we can keep improving our APIs while adhering to industry standards, as we have done very successfully until now. --Liran -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
