On Wed, 2013-06-26 at 15:22 -0700, David Miller wrote: > We've already been bitten by having things like the VXLAN port number > change on us after we've deployed the feature already. So this must > be finalized in a real RFC before I am willing to consider this patch. > > Also, I and everyone else, wants to see the user of these new flags > and behavior. That means you must post the entire SMC-R protocol stack > implementation at the time that you want this set of changes integrated. > > I'm not applying this patch until both of those issues are fully resolved. > > Thanks. > Dave, thanks for your response. I understand that you do not want to apply it this time when we do not have the using code ready. This will take us some more time. IBM intends to close the "Shared Memory Communications over RDMA" RFC [1] within a couple of months making it a published RFC, which should promote it into a status you would accept -- right? By the way, the TCP experimental option for SMC-R is already an official ID assigned from IANA [2]. Thus we are working on resolving both of your issues and intend to come back with this base tcp patch and its exploiting new address family in a few months. Kind regards, Ursula Braun [1] http://datatracker.ietf.org/doc/draft-fox-tcpm-shared-memory-rdma/ [2] http://www.iana.org/assignments/tcp-parameters -- To unsubscribe from this list: send the line "unsubscribe linux-s390" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
