Date: Thu, 16 Jun 2005 18:13:17 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: dragonfly dragonfly <dragonylffly@hotmail.com> Cc: freebsd-net@freebsd.org Subject: Re: LVS FreeBSD port Message-ID: <20050616180457.P27625@fledge.watson.org> In-Reply-To: <BAY19-F77572217F8CA5A82095C3DEF50@phx.gbl> References: <BAY19-F77572217F8CA5A82095C3DEF50@phx.gbl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 16 Jun 2005, dragonfly dragonfly wrote: > Recently i did a LVS FreeBSD port, and released 0.4.0 version > (http://dragon.linux-vs.org/~dragonfly/htm/lvs_freebsd.htm). It supports > LVS/DR and LVS/TUN with all LVS schedulers. Thanks must go to Clement > Laforet for committing it to ports/net/ipvs. > LVS(http://www.linuxvirtualserver.org/) is a widely used server > cluster schedule system, which is be included in Linux official kernel > 2.4 and 2.6 release. > Tests, bug report and fix, comments are very welcome. Li Wang, This looks like very interesting work. I'm confused, however, by the need for a kernel patch here -- it looks like the changes essentially center on allowing kernel modules to register new socket option handlers for sockets, and that the socket pointer itself isn't handed into the socket option handlers. I don't have a very complete understanding of the LVS kernel code yet, but my impression is that maybe you could simply substitute a sysctl for each of the get and set options, and avoid a patch entirely? Or perhaps the goal here is to minimize modifications to the userland netfilter admin tool? Thanks, Robert N M Watson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050616180457.P27625>