On Thu, Sep 12, 2013 at 10:22 AM, Jason Gunthorpe <jguntho...@obsidianresearch.com> wrote:
> On Thu, Sep 12, 2013 at 03:24:46PM +0300, Or Gerlitz wrote: > > Let me clarify this. The idea is that current RoCE applications will > > run as is after they update "their" librdmacm, since its this > > library that works with the new uverbs entries. > Or, we are not supposed to break userspace. You can't insist that a > user space library be updated in-sync with the kernel. Agree. This "IP based addressing" for RoCE looks like a big problem at the moment. Let me reiterate my understanding, and you guys can correct me if I get something wrong: - current addressing scheme is broken for virtualization use cases, because VMs may not know about what VLANs are in use. (also there are issues around bonding modes that use different Ethernet addresses) - proposed change requires: * all systems must update kernel at the same time, because old and new kernels cannot talk to each other * all systems must update librdmacm when they update the kernel, because old librdmacm does not work with new kernel I understand that we want to fix the issue around VLAN tagged traffic from VMs, but I don't see how we can break the whole stack to accomplish that. Isn't there some incremental way forward? - R. -- 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
