On 2/10/25 5:45 AM, zhangmingyi wrote:
From: Mingyi Zhang <zhangmingyi5@xxxxxxxxxx> Note that tcp_getsockopt and tcp_setsockopt support TCP_ULP, while bpf_getsockopt and bpf_setsockopt do not support TCP_ULP. I think we can add the handling of this case.
The commit message should talk about the "bool load" related changes in v2 and why it is needed.
The subject line is confusing. How about, "Support TCP_ULP in bpf_get/setsockopt" The code changes lgtm.
We want call bpf_setsockopt to replace the kernel module in the TCP_ULP case. The purpose is to customize the behavior in connect and sendmsg. We have an open source community project kmesh (kmesh.net). Based on this, we refer to some processes of tcp fastopen to implement delayed connet and perform HTTP DNAT when sendmsg.In this case, we need to parse HTTP packets in the bpf program and set TCP_ULP for the specified socket.