- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Wed, 25 Jun 2014 11:54:39 -0700
- To: Jason Greene <jason.greene@redhat.com>
- Cc: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
On 25 June 2014 11:42, Jason Greene <jason.greene@redhat.com> wrote: > I’m not sure they would. OSs tend to balk at application specific APIs and prefer reusable primitives. Even if an OS did though, it still has the cost of inserting frame headers every 16K, and that is not cheap. It also seems brittle to share the framing layer. I know of at least one major operating system that supports this sort of function already. And let's be clear: HTTP is important enough to allocate custom kernel resources to improve performance. I'd argue that it's important enough to dedicate silicon to eke out a few milliseconds or watts.
Received on Wednesday, 25 June 2014 18:55:11 UTC