From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id AB41FDE0 for ; Mon, 13 Feb 2017 17:02:35 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Feb 2017 08:02:34 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.35,156,1484035200"; d="scan'208,217";a="1125981885" Received: from irsmsx109.ger.corp.intel.com ([163.33.3.23]) by fmsmga002.fm.intel.com with ESMTP; 13 Feb 2017 08:02:32 -0800 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.173]) by IRSMSX109.ger.corp.intel.com ([169.254.13.44]) with mapi id 14.03.0248.002; Mon, 13 Feb 2017 16:02:29 +0000 From: "Dumitrescu, Cristian" To: Thomas Monjalon CC: "dev@dpdk.org" , "Richardson, Bruce" , "Yigit, Ferruh" , "Wiles, Keith" Thread-Topic: doc: deprecation notice for ethdev ops? Thread-Index: AdKGEnJImeSf75PfSge93vGG7Cw9Ag== Date: Mon, 13 Feb 2017 16:02:28 +0000 Message-ID: <3EB4FA525960D640B5BDFFD6A3D891265274BEE4@IRSMSX108.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNzdjZTJjOTctZmRlZS00MTZmLWI3YzItZDg4MzVkMWMyZmY4IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjIuMTEuMCIsIlRydXN0ZWRMYWJlbEhhc2giOiJ0WCtzenpKaTNVakVxT0dIclwvWTlVbFRGcEtMMnBtVUlNNGdaWCtXUHRTcz0ifQ== x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.180] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] doc: deprecation notice for ethdev ops? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2017 16:02:36 -0000 Hi Thomas, When a new member (function pointer) is added to struct eth_dev_ops (as the= last member), does it need to go through ABI chance process (e.g. chance n= otice one release before)? IMO the answer is no: struct eth_dev_ops is marked as internal and its inst= ances are only accessed through pointers, so the rte_eth_devices array shou= ld not be impacted by the ops structure expanding at its end. Unless there = is something that I am missing? My question is in the context of this patch under review for 17.5 release: = http://www.dpdk.org/ml/archives/dev/2017-February/057367.html. Thanks, Cristian