Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754898Ab0HXOvl (ORCPT ); Tue, 24 Aug 2010 10:51:41 -0400 Received: from mail-ew0-f46.google.com ([209.85.215.46]:50723 "EHLO mail-ew0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753154Ab0HXOve (ORCPT ); Tue, 24 Aug 2010 10:51:34 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=oqKcmK2ou5aAaDguC980xeYPpv2GRpjAobGQ1cbkbyBwatn8wuXr/PGiHFyj9jrn9w dTMMvjek4mcy7ZOjgcd+tzd+4SyVgiQX7E100ql17ToaJn6I/jk7jSpXBQQvvcX1GBlN qX8cUqVcPwQLK0DuQ6OPnpPkbqSdxJ+XpPIEk= MIME-Version: 1.0 In-Reply-To: <4C73DA15.2010207@vlnb.net> References: <594039.74663.qm@web111905.mail.gq1.yahoo.com> <1282144271.3035.31.camel@mulgrave.site> <1282148296.3035.49.camel@mulgrave.site> <4C6C1D70.7020502@vlnb.net> <41A1E2691BBB412BADCDE5F515CD8EDA@usish.com.cn> <8A96806D-6CD7-44AD-8A9D-143C098C95A4@uni-paderborn.de> <1282256949.30453.278.camel@haakon2.linux-iscsi.org> <4C701E08.2020005@vlnb.net> <1282423398.3015.39.camel@mulgrave.site> <4C73DA15.2010207@vlnb.net> From: Chris Weiss Date: Tue, 24 Aug 2010 09:51:04 -0500 Message-ID: Subject: Re: [Scst-devel] Fwd: Re: linuxcon 2010... To: Vladislav Bolkhovitin Cc: James Bottomley , Mike Christie , linux-scsi@vger.kernel.org, Chetan Loke , linux-kernel@vger.kernel.org, scst-devel Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1229 Lines: 24 On Tue, Aug 24, 2010 at 9:41 AM, Vladislav Bolkhovitin wrote: > James Bottomley, on 08/22/2010 12:43 AM wrote: >> Interface re-use (or at least ABI compatibility) is the whole point, >> it's what makes the solution a drop in replacement. > > I see now. You want ABI compatibility to keep the "contract" that no > kernel changes can break applications binary compatibility for unlimited > time. ok now I'm confused, or maybe I'm not understanding ABI correctly, or maybe you guys are using it in a way that is inconsistent with popular convention. As a VMware user, I have experienced fully that the kernel ABI changes in various places with every release. VMwares drivers have to be constantly updated to match changes in kernel function parameters and even what functions are available. I've also experienced it with scsi cards, dsl modems, and other 3rd party drivers. It's the one big downside to developing for the Linux kernel, the ABI is /always/ changing. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/