From owner-freebsd-net@FreeBSD.ORG Thu Jun 16 17:11:05 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8144E16A41C for ; Thu, 16 Jun 2005 17:11:05 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 594BA43D48 for ; Thu, 16 Jun 2005 17:11:05 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id A182746B0E; Thu, 16 Jun 2005 13:11:04 -0400 (EDT) Date: Thu, 16 Jun 2005 18:13:17 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: dragonfly dragonfly In-Reply-To: Message-ID: <20050616180457.P27625@fledge.watson.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: LVS FreeBSD port X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jun 2005 17:11:05 -0000 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