From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Julius Volz" Subject: Re: [PATCH 00/26] IPVS: Add first IPv6 support to IPVS. Date: Thu, 12 Jun 2008 17:34:04 +0200 Message-ID: References: <48501C81.6010800@trash.net> <48502826.9060502@trash.net> <48503BBD.6000307@google.com> <485043E6.5030105@candelatech.com> <485050FE.6030209@google.com> <20080612014548.GE22358@verge.net.au> <485126BD.7030109@trash.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "Simon Horman" , "Vince Busam" , "Ben Greear" , lvs-devel@vger.kernel.org, netdev@vger.kernel.org To: "Patrick McHardy" Return-path: In-Reply-To: <485126BD.7030109@trash.net> Content-Disposition: inline Sender: lvs-devel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Thu, Jun 12, 2008 at 3:38 PM, Patrick McHardy wrote: > Julius Volz wrote: >>> I wonder if now would be a good time to bite the bullet and design >>> a new interface that is extendable. >> >> If we really have to break it once for IPv6 anyways, it seems like a >> good opportunity. Depends on how invasive the changes would need to >> be, of course... > > You don't need to break the old interface, just add an additional > one. Ok, then we will just keep the old one in parallel for some time. >> You probably already have some ideas on what a better interface would >> look like? Especially, how to design it for future backwards >> compatibility? And would it still use sockopts or rather one of the >> other communication mechanisms? > > I'd suggest genetlink or nfnetlink. Ah, that's what I thought... Are there any simple kernel examples with userspace counterparts to look at? I know iproute2 uses netlink, but it seems like a rather complicated example. Genetlink seems especially nice, although I couldn't find a general explanation of it other than in git history. Julius -- Google Switzerland GmbH