Date: Sat, 31 Oct 2015 16:44:20 -0700 From: Randall Stewart <rrs@netflix.com> To: FreeBSD Transports <transport@FreeBSD.org> Subject: Modular TCP .. or the start.. Message-ID: <1180181A-03CE-48FB-BC52-1606AF1EFBD3@netflix.com>
next in thread | raw e-mail | index | archive | help
All: As promised I managed to get working this afternoon a modular transport = much on the lines of what we have talked about. The review of it is here: https://reviews.freebsd.org/D4055 There are still things left un-done .. but its a first step that covers = quite a bit and I also supply a KLM called fastpath that shows how it can be used = and adds two different fast-path approaches we have tried at Netflix (we may be = moving completely to the fastack version). There is also a utility included in usr.sbin that allows you to list and = manipulate whats in the system (i.e. see the default, set the default, show all entries). = An individual socket can also set its own TCP function set at open (but not after it = has moved to some other state). There are a few things missing that Jonathan wanted in particular I did = *not* do tcp_input() or pru_usrreq() These would involve a lot more work in the in_pcb and I did not want to = tackle that yet=85 it can be something we add later.. there is enough here that I think a lot can = be done to play with new tcp stacks and alternate designs :-) Please look and make comments, the usual suspects on the transport = review are named as reviewers Best wishes R -------- Randall Stewart rrs@netflix.com 803-317-4952
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1180181A-03CE-48FB-BC52-1606AF1EFBD3>