Date: Wed, 10 Aug 2011 10:06:20 +0300 From: Catalin Nicutar <catalin.nicutar@gmail.com> To: soc-status@freebsd.org Subject: TCP UTO - Weekly Report 10 Message-ID: <CADgY63vLbGdp3euJtmh_2H4j97dAM4f6xmohNmiev_o6HztpqA@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hello! This is the tenth report for TCP UTO. * Short TCP UTO description UTO stands for User Timeout Option (it is described in RFC5482). TCP UTO specifies a peer should be allowed to advertise its chosen `User Timeout' for a connection. The wiki page for this project: http://wiki.freebsd.org/CatalinNicutar/TCPUTO * Work completed last week * I have forward-ported to HEAD both kernel changes and telnet, openssh and netcat * I have added UTO support to varnishd 3.0.0. The option is sent when the sess_timeout parameter is used * I have made a small change to the way the received timeout is handled by passive sockets * I have developed a scenario in which a careless server ties the resources of a machine to the point that no other process can use sockets any more, and pinpointed the exact cause * My goals for this week * I will try to periodically drop misbehaving connections such that the scenario above is impossible * I will change the handling of the TCP_RCVUTO_TIMEOUT socket option to allow a process to specify a per-connection limit If you have questions, suggestions or advices drop me an email to cnicutar@FreeBSD.org. Catalin Nicutar
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADgY63vLbGdp3euJtmh_2H4j97dAM4f6xmohNmiev_o6HztpqA>