From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jing.d.chen@intel.com>
Received: from mga11.intel.com (mga11.intel.com [192.55.52.93])
 by dpdk.org (Postfix) with ESMTP id A796C6932
 for <dev@dpdk.org>; Thu,  9 Feb 2017 03:23:46 +0100 (CET)
Received: from fmsmga002.fm.intel.com ([10.253.24.26])
 by fmsmga102.fm.intel.com with ESMTP; 08 Feb 2017 18:23:45 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.35,349,1484035200"; d="scan'208";a="1124049352"
Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205])
 by fmsmga002.fm.intel.com with ESMTP; 08 Feb 2017 18:23:45 -0800
Received: from fmsmsx156.amr.corp.intel.com (10.18.116.74) by
 fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Wed, 8 Feb 2017 18:23:45 -0800
Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by
 fmsmsx156.amr.corp.intel.com (10.18.116.74) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Wed, 8 Feb 2017 18:23:45 -0800
Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.88]) by
 SHSMSX101.ccr.corp.intel.com ([169.254.1.177]) with mapi id 14.03.0248.002;
 Thu, 9 Feb 2017 10:23:42 +0800
From: "Chen, Jing D" <jing.d.chen@intel.com>
To: "Wiles, Keith" <keith.wiles@intel.com>, Stephen Hemminger
 <stephen@networkplumber.org>
CC: "dev@dpdk.org" <dev@dpdk.org>, "Rogers, Gerald" <gerald.rogers@intel.com>
Thread-Topic: [dpdk-dev] [RFC 2/2] prgdev: introduce generic prgdev API
Thread-Index: AQHScwd1na1KQNYWW0ab0T+Gx1c04qFfTx2AgAAEx4CAALzYsA==
Date: Thu, 9 Feb 2017 02:23:42 +0000
Message-ID: <4341B239C0EFF9468EE453F9E9F4604D3C5EEA1D@shsmsx102.ccr.corp.intel.com>
References: <1484882498-18653-1-git-send-email-jing.d.chen@intel.com>
 <1484882498-18653-3-git-send-email-jing.d.chen@intel.com>
 <20170208144945.0ce116ee@xeon-e3>
 <EABD0B8C-FECB-4E7D-99D8-6268A1324C9C@intel.com>
In-Reply-To: <EABD0B8C-FECB-4E7D-99D8-6268A1324C9C@intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.239.127.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dpdk-dev] [RFC 2/2] prgdev: introduce generic prgdev API
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 02:23:47 -0000

Hi, Keith, Stephen,

> -----Original Message-----
> From: Wiles, Keith
> Sent: Thursday, February 9, 2017 7:07 AM
> To: Stephen Hemminger <stephen@networkplumber.org>
> Cc: Chen, Jing D <jing.d.chen@intel.com>; dev@dpdk.org; Rogers, Gerald
> <gerald.rogers@intel.com>
> Subject: Re: [dpdk-dev] [RFC 2/2] prgdev: introduce generic prgdev API
>=20
>=20
> > On Feb 8, 2017, at 4:49 PM, Stephen Hemminger
> <stephen@networkplumber.org> wrote:
> >
> > On Fri, 20 Jan 2017 11:21:38 +0800
> > "Chen Jing D(Mark)" <jing.d.chen@intel.com> wrote:
> >
> >> +struct rte_prg_dev_info {
> >> +	struct rte_pci_device *pci_dev; /**< Device PCI information. */
> >
> > NAK
> >
> > No new API should refer to PCI devices. We are trying to make all
> > references to devices generic. Crypto suceeded, ether is in process, bu=
t no
> new ones please.
>=20
> The design is not PCI centric and should not be PCI centric, it is just w=
hat they
> started with months ago. So please look past the PCI bits as they have no=
t
> integrated into the latest code base yet.
>=20

I got you. Will remove the reference in formal patch.