Re: #540: "jumbo" frames

I don't see how CONTINUATION makes a hardware implementation more
difficult, though?
It doesn't at all change the buffer management.
-=R


On Wed, Jun 25, 2014 at 1:20 PM, Poul-Henning Kamp <phk@phk.freebsd.dk>
wrote:

> In message <CAP+FsNcwTBLjn+CV0gnrpG_87U=
> xetOJsqoyFF5Ze+w_Ucwfpg@mail.gmail.com>
> , Roberto Peon writes:
>
> >Look at this from a hardware engineer's perspective. This bit changes how
> >you must structure hardware buffers in order to parse things properly.
> >This requires far more complexity for a hardware implementation, and would
> >reduce the chance that we get acceleration in HW for HTTP2.
>
> But the elimination of CONTINUATION would more than offset that minor
> bit of complexity.
>
>
> --
> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> phk@FreeBSD.ORG         | TCP/IP since RFC 956
> FreeBSD committer       | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
>

Received on Wednesday, 25 June 2014 20:24:33 UTC