From: Ursula Braun <ubr...@linux.vnet.ibm.com> Date: Fri, 21 Aug 2015 13:30:27 +0200
> this is V4 of my SMC-R patches: > Since you are asking for a solution "100% in our own separate module > with our own can of worms", we have to give up the transparent detection > whether a communication peer can do SMC-R or not (this has been the > purpose of the rejected TCP hooks). Instead, we want just the new > self-contained SMC-R socket family added to the kernel. > By the way, since August 2015 the SMC-R Informational RFC is no longer > a draft, but published as RFC7609. The tcp_set_keepalive() layering hack is still beyond what I'm willing to apply, sorry. Also, as a coding style note, all of your code needs to be adjusted to declare local function variables in "reverse christimas tree" order, that is longest line to shortest. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
