From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58]) by dpdk.org (Postfix) with ESMTP id EA090156 for ; Wed, 9 Apr 2014 20:38:19 +0200 (CEST) Received: from hmsreliant.think-freely.org ([2001:470:8:a08:7aac:c0ff:fec2:933b] helo=localhost) by smtp.tuxdriver.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.63) (envelope-from ) id 1WXxPd-0004si-P7 for dev@dpdk.org; Wed, 09 Apr 2014 14:39:56 -0400 Date: Wed, 9 Apr 2014 14:39:52 -0400 From: Neil Horman To: dev@dpdk.org Message-ID: <20140409183952.GA16493@hmsreliant.think-freely.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Score: -2.9 (--) X-Spam-Status: No Subject: [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 18:38:20 -0000 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. Thoughts? Neil