From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Hunt, David" Subject: Re: [PATCH v3] mempool: reduce rte_mempool structure size Date: Mon, 15 Feb 2016 09:58:52 +0000 Message-ID: <56C1A15C.8060603@intel.com> References: <1455039006-86816-1-git-send-email-keith.wiles@intel.com> <56BDEA08.9040402@redhat.com> <09D5A01F-7205-49E8-9A27-95161235963E@intel.com> <10558998.3znIRhOpQL@xps13> <56BDFF2B.5090401@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Olivier MATZ , Thomas Monjalon , "Wiles, Keith" Return-path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 301D5592A for ; Mon, 15 Feb 2016 10:58:56 +0100 (CET) In-Reply-To: <56BDFF2B.5090401@6wind.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 12/02/2016 15:50, Olivier MATZ wrote: > - NEXT_ABI does make the code harder to read in this case, and I'm > thinking about the patchset from David Hunt (external mempool handler) > that will be in the same situation, and maybe also another patchset > I'm working on. Olivier, I'm working on that at the moment with the external mempool handler code. However, it crossed my mind that we have a choice to use symbol versioning OR use NEXT_ABI. Would one method be preferred over the other? Regards, David.