From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id C31065A6C for ; Wed, 15 Jul 2015 13:36:39 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga103.fm.intel.com with ESMTP; 15 Jul 2015 04:36:11 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,479,1432623600"; d="scan'208";a="729301621" Received: from orsmsx103.amr.corp.intel.com ([10.22.225.130]) by orsmga001.jf.intel.com with ESMTP; 15 Jul 2015 04:36:12 -0700 Received: from fmsmsx111.amr.corp.intel.com (10.18.116.5) by ORSMSX103.amr.corp.intel.com (10.22.225.130) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 15 Jul 2015 04:36:10 -0700 Received: from FMSMSX110.amr.corp.intel.com ([169.254.14.199]) by fmsmsx111.amr.corp.intel.com ([169.254.12.65]) with mapi id 14.03.0224.002; Wed, 15 Jul 2015 04:36:10 -0700 From: "Wang, Liang-min" To: Thomas Monjalon Thread-Topic: [dpdk-dev] [PATCH v15 1/4] ethdev: add apis to support access device info Thread-Index: AQHQvdt1mqDlF89RhkqcFpoATAtfap3chRkA///IeeCAAH2pgP//j7ZAgAB/NAD//4yPAA== Date: Wed, 15 Jul 2015 11:36:10 +0000 Message-ID: References: <1432946276-9424-1-git-send-email-liang-min.wang@intel.com> <4907797.WMXsT5lYd9@xps13> <1436962741.PL5XZBfjSs@xps13> In-Reply-To: <1436962741.PL5XZBfjSs@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.200.107] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH v15 1/4] ethdev: add apis to support access device info 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, 15 Jul 2015 11:36:40 -0000 > -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: Wednesday, July 15, 2015 7:21 AM > To: Wang, Liang-min > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH v15 1/4] ethdev: add apis to support acces= s > device info >=20 > 2015-07-15 10:48, Wang, Liang-min: > > > > > What means magic? Is it always a device id? > > > > This field is the same as defined in kernel ethtool data structure. > > > > > > Not an excellent argument :) > > > Actually you didn't answer. > > > > > I could not speak for other devices. For igb and ixgbe, it's device id. > > Based upon literature search, this field is used by device driver to pr= ovide > extra information. > > What would be your suggestion? >=20 > I don't have any suggestion. > You are defining a new API in DPDK, so our concern must be to check > that it will be easily understood by users and PMD developers. > If you don't really know what this field will be for, others won't know. No, I meant it's device driver dependent.=20 If I keep the same naming convention following kernel ethtool defined, and adding comment like "device-specific magic key, such as device-id". Would that be acceptable from you? This data structure is defined to be compatible with kernel ethtool API, and magic key is device specific and known to ethtool API users.