From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 8D560548B for ; Wed, 21 Jun 2017 11:23:01 +0200 (CEST) Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga104.jf.intel.com with ESMTP; 21 Jun 2017 02:23:00 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,368,1493708400"; d="scan'208";a="100054272" Received: from irsmsx151.ger.corp.intel.com ([163.33.192.59]) by orsmga004.jf.intel.com with ESMTP; 21 Jun 2017 02:22:59 -0700 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.133]) by IRSMSX151.ger.corp.intel.com ([169.254.4.191]) with mapi id 14.03.0319.002; Wed, 21 Jun 2017 10:22:58 +0100 From: "Iremonger, Bernard" To: Stephen Hemminger CC: "dev@dpdk.org" , "thomas@monjalon.net" Thread-Topic: [dpdk-dev] [PATCH v2 1/4] ethdev: modify callback process API Thread-Index: AQHS448wRdXwbllne0asf82QKEvsq6ImBEAAgAkPxvA= Date: Wed, 21 Jun 2017 09:22:58 +0000 Message-ID: <8CEF83825BEC744B83065625E567D7C24E0197CB@IRSMSX108.ger.corp.intel.com> References: <1495191794-9112-1-git-send-email-bernard.iremonger@intel.com> <1497280691-18641-2-git-send-email-bernard.iremonger@intel.com> <20170615084300.00e95ddc@xeon-e3> In-Reply-To: <20170615084300.00e95ddc@xeon-e3> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNGZkNTM3ODUtNjdiNS00YWYyLTk5NjctN2IzY2U0OTM1NTlmIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6InVhT0ltTUZDWDc3bkUwb2NDVTBhbHM1aVI4RkluRVlcL1AzOGZod01hUE9NPSJ9 x-ctpclassification: CTP_IC dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v2 1/4] ethdev: modify callback process API 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: Wed, 21 Jun 2017 09:23:02 -0000 Hi Stephen, > -----Original Message----- > From: Stephen Hemminger [mailto:stephen@networkplumber.org] > Sent: Thursday, June 15, 2017 4:43 PM > To: Iremonger, Bernard > Cc: dev@dpdk.org; thomas@monjalon.net > Subject: Re: [dpdk-dev] [PATCH v2 1/4] ethdev: modify callback process AP= I >=20 > On Mon, 12 Jun 2017 16:18:08 +0100 > Bernard Iremonger wrote: >=20 > > From: "Bernard.Iremonger" > > > > Change the rte_eth_dev_callback_process function to return int, and > > add a void *ret_param parameter. >=20 > What is the motivation for this? What is return value used for? Since DPDK 16.11 the i40e and ixgbe PMD's have been returning data to the c= alling process using the "void *cb_arg" parameter of the callback_process = API void _rte_eth_dev_callback_process(struct rte_eth_dev *dev, enum rte_eth_ev= ent_type event, void *cb_arg); This was not considered to be ideal by Thomas who suggested adding a "void = *ret_param" parameter to API to return data to the calling process and at= the same time to change the return value from void to int to allow returni= ng an error code if required. =20 Regards, Bernard.