From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pb0-f45.google.com (mail-pb0-f45.google.com [209.85.160.45]) by dpdk.org (Postfix) with ESMTP id 8B881137D for ; Wed, 9 Apr 2014 23:07:15 +0200 (CEST) Received: by mail-pb0-f45.google.com with SMTP id uo5so3011947pbc.4 for ; Wed, 09 Apr 2014 14:08:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=wAFSmwbVA+CsgZji0Xe3ogihPvRlFJ0xuHNR9f4lopw=; b=jjShecB5s59YCQlbWoJp3rW1EAI2AF1FDhUFoTnb9KkaA3/6xKZmI57qoB5vRzGKQm 00BKCbFiLWiKMe9PryqG1CPT4sOTrx9HQXISVSB9aodD6A3mCIIKNE2IUMdujZJkYUOo zmmbt7npC/eSamPLzpaWUJ2JfI4l+6fhws+lNk6W8tR6utR7lfv366HjF29A5piyQbFB LDGdgsyYJ9/o5NjvW48GNWkctvdFA5uvZXCOIkL4yVPfn45dKBnsgQ9UcEUNOsz5FPf7 Zt9HSywkw2lpJR0ftXjuFO9eygUekl1n/cQZEb5kVRnYGIZ1zys/uszmLE6artpFm13i rsTg== X-Gm-Message-State: ALoCoQmeZjBpgfOx1oanFPVRr8uti6JQ3Wm9yKmd1BFUHkvsN3NV3BQwoxALdegL0le1WPsfrEdu X-Received: by 10.66.141.197 with SMTP id rq5mr15091525pab.64.1397077732204; Wed, 09 Apr 2014 14:08:52 -0700 (PDT) Received: from nehalam.linuxnetplumber.net (static-50-53-83-51.bvtn.or.frontiernet.net. [50.53.83.51]) by mx.google.com with ESMTPSA id tu3sm10148968pab.1.2014.04.09.14.08.51 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Wed, 09 Apr 2014 14:08:51 -0700 (PDT) Date: Wed, 9 Apr 2014 14:08:49 -0700 From: Stephen Hemminger To: Neil Horman Message-ID: <20140409140849.176db9be@nehalam.linuxnetplumber.net> In-Reply-To: <20140409183952.GA16493@hmsreliant.think-freely.org> References: <20140409183952.GA16493@hmsreliant.think-freely.org> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org Subject: Re: [dpdk-dev] DPDK API/ABI Stability X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Apr 2014 21:07:16 -0000 On Wed, 9 Apr 2014 14:39:52 -0400 Neil Horman wrote: > Hey all- > I was going to include this as an addendum to the packaging thread on > this list, but I can't seem to find it in my inbox, so forgive me starting a new > one. > > I wanted to broach the subject of ABI/API stability on the list here. > Given the recent great efforts to make dpdk packagable by disributions, I think > we probably need to discuss API stability in more depth and come up with a plan > to implement it. Has anyone started looking into this? If not, it seems to me > to be reasonable to start by placing a line in the sand with the functions > documented here: > > http://dpdk.org/doc/api/ > > It seems to me we can start reviewing the API library by library, enusring only > those functions are exported, making sure the data types are appropriate for > export, and marking them with a linker script to version them appropriately. To what level? source? binary, internal functions? Some of the API's could be stablized without much impact but others such as the device driver interface is incomplete and freezing it would make live hard.