From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vincent JARDIN Subject: Re: [dpdk-announce] important design choices - statistics - ABI Date: Thu, 18 Jun 2015 23:13:56 +0200 Message-ID: <55833494.9050804@6wind.com> References: <9092314.MoyqUJ5VU2@xps13> <26FA93C7ED1EAA44AB77D62FBE1D27BA54D6D24C@IRSMSX102.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: "dev@dpdk.org" To: "O'Driscoll, Tim" , Thomas Monjalon Return-path: Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by dpdk.org (Postfix) with ESMTP id 8407AC62A for ; Thu, 18 Jun 2015 23:13:58 +0200 (CEST) Received: by wilj4 with SMTP id j4so1576523wil.0 for ; Thu, 18 Jun 2015 14:13:58 -0700 (PDT) In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA54D6D24C@IRSMSX102.ger.corp.intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 18/06/2015 18:55, O'Driscoll, Tim wrote: > I like Olivier's proposal on using a single option (CONFIG_RTE_NEXT_ABI) to control all of these changes instead of a separate option per patch set (seehttp://dpdk.org/ml/archives/dev/2015-June/019147.html), so I think we should rework the affected patch sets to use that approach for 2.1. Do we have any other options to meet the short deadlines of 2.1?