SOCKMAP - TCP splicing of the future(blog.cloudflare.com)
blog.cloudflare.com
SOCKMAP - TCP splicing of the future
https://blog.cloudflare.com/sockmap-tcp-splicing-of-the-future/
10 comments
The ambitious thing to do would be to eliminate the kernel/user space boundary entirely and support their use case entirely in ring0. God, I wish I worked there. I don't know enough about the details of their use case to do it out in the open.
sockmap has been through a lot of changes since then. Some done by CF (hi Jakub!) some by others, including bytedance and isovalent.
Recently there has been a push to figure out the backpressure situation, so it's worth checking again.
Marek
Recently there has been a push to figure out the backpressure situation, so it's worth checking again.
Marek
You are far better off reading the sockmap docs than this post, it adds almost nothing, entirely fails to explain the point of the interface and more or less amounts to marketing slop
(2019)
TLDR, not ready for prime time.
Sadly, probably still the best Cloudflare blog written in the last nine months.
Sadly, probably still the best Cloudflare blog written in the last nine months.
Article is from 2019.
Hello Claude!
[deleted]
Since it's from 2019, it shows that your detector is not to be believed. Sorry, yo.
Interestingly, HN also appears to be Claude. My comment was 5 days ago, along with the post. But now it's showing as 15 hours ago. It still says 5 days on my comments list though.
(The Claude reference was because dates utterly confound it)
(The Claude reference was because dates utterly confound it)