On Tue, Dec 8, 2015 at 11:59 AM, Tom Herbert <t...@herbertland.com> wrote: > On Tue, Dec 8, 2015 at 11:31 AM, John W. Linville > <linvi...@tuxdriver.com> wrote: >> On Tue, Dec 08, 2015 at 10:27:18AM -0800, Tom Herbert wrote: >>> Add support for remote checksum offload in both the normal and GRO >>> paths. netlink command are used to enable sending of the Remote >>> Checksum Data, and allow processing of it on receive. The Remote >> > Extraneous. > >> afsO&^(*&5^a+++NO CARRIER >> >> Did you mean to finish that sentence? ;-) >> >>> Signed-off-by: Tom Herbert <t...@herbertland.com> >> >> Jesse is going to have to comment on your (ab)use of the reserved >> fields. I presume that an RFC would be forthcoming? >> > I'll spin an I-D once there is agreement on the approach. This is > identical to VXLAN excepted the bit flag indicating csum_start is > present might be different.
Thanks for doing this - it was also on my to-do list. We can definitely do better than VXLAN here since there is extensibility built into the protocol. I think the right way to do this is to define a TLV option and then use the same format as what you defined for GUE (and it is also nice to reuse some of the option formats to minimize differences across protocols). I'd like to set up an IANA registry for classes but that's a little slow going at this point, so for the next draft update I'm planning on adding some initial assignments, including a Linux class. We could then allocate remote checksum out of that. The new version of the draft should be coming out pretty soon. -- 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
