3 ms·
SOCKMAP - TCP splicing of the future
- walth 4mo agoTLDR, not ready for prime time. Sadly, probably still the best Cloudflare blog written in the last nine months.
- throwaway67743 4mo agoHello Claude!
- deleted 4mo ago[deleted]
- fragmede 4mo agoSince it's from 2019, it shows that your detector is not to be believed. Sorry, yo.
- throwaway67743 4mo agoInterestingly, 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)
- lmz 4mo agoArticle is from 2019.
- majke 4mo agosockmap 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
- eqvinox 4mo ago(2019)
- 100ms 4mo agoYou 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
- fragmede 4mo agoThe 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.