From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jim.st.leger@intel.com>
Received: from mga14.intel.com (mga14.intel.com [143.182.124.37])
 by dpdk.org (Postfix) with ESMTP id 37A2B3F9
 for <dev@dpdk.org>; Mon,  6 Jan 2014 17:22:02 +0100 (CET)
Received: from fmsmga001.fm.intel.com ([10.253.24.23])
 by azsmga102.ch.intel.com with ESMTP; 06 Jan 2014 08:23:12 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.95,613,1384329600"; d="scan'208";a="454321754"
Received: from fmsmsx108.amr.corp.intel.com ([10.19.9.228])
 by fmsmga001.fm.intel.com with ESMTP; 06 Jan 2014 08:23:12 -0800
Received: from FMSMSX109.amr.corp.intel.com (10.18.116.9) by
 FMSMSX108.amr.corp.intel.com (10.19.9.228) with Microsoft SMTP Server (TLS)
 id 14.3.123.3; Mon, 6 Jan 2014 08:23:12 -0800
Received: from fmsmsx114.amr.corp.intel.com ([169.254.6.202]) by
 FMSMSX109.amr.corp.intel.com ([169.254.5.203]) with mapi id 14.03.0123.003;
 Mon, 6 Jan 2014 08:23:12 -0800
From: "St Leger, Jim" <jim.st.leger@intel.com>
To: "TSADOK, Shlomi (Shlomi)" <shlomi.tsadok@alcatel-lucent.com>, "Thomas
 Monjalon" <thomas.monjalon@6wind.com>
Thread-Topic: [dpdk-dev] Specific NIC for DPDK?
Thread-Index: Ac8K14gmqd4g6ZjCSo6fi9ZjFQQ1FgATyUUAAARvUYAAAB5AAAAPXuqQ
Date: Mon, 6 Jan 2014 16:23:11 +0000
Message-ID: <00B2C372B6E6DA4FB04934511BF0564A3DF33896@FMSMSX114.amr.corp.intel.com>
References: <70ED7DF10DA6754880C553B2CD6E25230AB45B@FR712WXCHMBA13.zeu.alcatel-lucent.com>
 <CA+8v-JxpMrwwD3O4VZ+gE=cvMyKcy9QGSZhZGK2o+mW9YLjnFw@mail.gmail.com>
 <201401061638.36025.thomas.monjalon@6wind.com>
 <70ED7DF10DA6754880C553B2CD6E25230ADF9A@FR712WXCHMBA13.zeu.alcatel-lucent.com>
In-Reply-To: <70ED7DF10DA6754880C553B2CD6E25230ADF9A@FR712WXCHMBA13.zeu.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.200.106]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Specific NIC for DPDK?
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <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: Mon, 06 Jan 2014 16:22:02 -0000

You could write a PMD for any NIC. The work is only done for the NICs liste=
d here http://dpdk.org/doc/nics
But nothing stopping anyone from using other NICs if they want to write the=
 PMD.

Regards,
Jim

-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of TSADOK, Shlomi (Shlomi=
)
Sent: Monday, January 06, 2014 8:42 AM
To: Thomas Monjalon
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Specific NIC for DPDK?

Thanks guys

So basically "only" Intel* and mlx4 are supported? Do I get it right?


Regards
Shlomi


-----Original Message-----
From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
Sent: Monday, January 06, 2014 5:39 PM
To: TSADOK, Shlomi (Shlomi)
Cc: dev@dpdk.org; Daniel Kaminsky
Subject: Re: [dpdk-dev] Specific NIC for DPDK?

06/01/2014 14:31, Daniel Kaminsky :
> Currently DPDK supports most of Intel 1Gb and 10Gb NICs. The exact=20
> list can be found at lib/librte_eal/common/include/rte_pci_dev_ids.h

There are more supported NICs than in rte_pci_dev_ids.h.
Please have a look at the online documentation:
	http://dpdk.org/doc/nics

--
Thomas