A reworked TCP zero-copy receive API

Posted May 19, 2018 11:48 UTC (Sat) by grawity (subscriber, #80596)
In reply to: A reworked TCP zero-copy receive API by jhoblitt
Parent article: A reworked TCP zero-copy receive API

I'd say the performance requirements for mmapping a few dozen libraries once per exec don't come anywhere close to mmapping a million packets per second...

A reworked TCP zero-copy receive API

Posted May 19, 2018 13:50 UTC (Sat) by jhoblitt (subscriber, #77733) [Link] (1 responses)

The reworked API only has one mmap() call to setup the window. I'm not really grasping what the concern on this thread is.

A reworked TCP zero-copy receive API

Posted May 19, 2018 21:43 UTC (Sat) by eternaleye (guest, #67051) [Link]

You're missing that this thread isn't about a _design_ concern with the _new_ proposal, it's a _process_ concern regarding the _old_ proposal (which did call mmap() once per receive). Namely, "How did that proposal get so far along before someone noticed that issue?"