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: Wed, 11 Jun 2008 21:29:16 +0200 Message-ID: References: <1213204329-10973-1-git-send-email-juliusv@google.com> <48500A0D.5020304@trash.net> <48501C81.6010800@trash.net> <4850233E.7090501@trash.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: lvs-devel@vger.kernel.org, netdev@vger.kernel.org To: "Patrick McHardy" Return-path: In-Reply-To: <4850233E.7090501@trash.net> Content-Disposition: inline Sender: lvs-devel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Wed, Jun 11, 2008 at 9:10 PM, Patrick McHardy wrote: > Julius Volz wrote: >> ipvsadm uses get/set-sockopts on a raw socket to pass commands and >> structs (as defined in include/net/ip_vs.h) to the kernel. So the >> passed structs have to match exactly between userspace and kernel. The >> kernel ip_vs.h also includes a version number that is used to verify >> that ipvsadm matches your kernel version. > > So they define an ABI, which means they must not be changed in > incompabtible ways. The question is whether they are actually > changed in incomaptible ways. It is clearly laid out to be able to be changed over time, hence the ipvsadm version check... I think this whole interface is quite an exception though. Julius -- Google Switzerland GmbH