TCP: Fast-Open observability
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v1 Latest posting 2/22 patches 9 repliesIn review
- v1 RFC posting 1/22 patches 0 repliesSuperseded
Patches in v1 posting 2/2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | TCP: note received valid-cookie Fast Open optioninclude/ net/ | +3 | 4 replies | |
| 2/2 | TCP: pass accepted-TFO indication through getsockoptinclude/ net/ | +3 | 5 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RESEND PATCH 0/2] TCP: Fast-Open observability
Whether TCP Fast Open was used for a connection is not reliably observable by an accepting application when the SYN passed no data.
Fix this by noting during SYN receive processing that an acceptable Fast Open option was used, and provide this to userland via getsockopt TCP_INFO.
Jeremy Harris (2):
TCP: note received valid-cookie Fast Open option
TCP: pass accepted-TFO indication through getsockopt
include/linux/tcp.h | 3 ++- include/uapi/linux/tcp.h | 1 + net/ipv4/tcp.c | 2 ++ net/ipv4/tcp_fastopen.c | 1 + 4 files changed, 6 insertions(+), 1 deletion(-)
base-commit: 24e31e4747698dc50d408f0082d7eb9b9520d2f6
Signature · 1 line
2.49.0