Rémi Denis-Courmont wrote:
By the way, couldn't encap_type be remove altogether (using two slightly different callbacks for ESP) from udp_sock?
The notion of encap_type is needed for the setsockopt call so it would have to stay in the API. If it were removed from udp_sock, getsockopt would have to derive the encap_type from encap_rcv funcptr values, which would be messy. I think it might complicate the logic in ESP too.
-- James Chapman Katalix Systems Ltd http://www.katalix.com Catalysts for your Embedded Linux software development - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html