DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Helin" <helin.zhang@intel.com>
To: ayon jyoti Biswas <ajbiswas2009@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] How to run intel dpdk apps on '82574L Gigabit Network Connection' NIC cards
Date: Thu, 15 Jan 2015 07:24:24 +0000	[thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A7E8D8B@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <CABq0x8RZmUHSqACMssXD001Za=1b2KGU2dfOZpQdchTxZRsQTA@mail.gmail.com>

Hi Ayon

1521 is the device ID of my NIC, yours is 10d3. So you need to check if 10d3 is listed in that file or not, but not checking 1521.

Regards,
Helin

From: ayon jyoti Biswas [mailto:ajbiswas2009@gmail.com]
Sent: Thursday, January 15, 2015 3:19 PM
To: Zhang, Helin
Subject: Re: [dpdk-dev] How to run intel dpdk apps on '82574L Gigabit Network Connection' NIC cards

hi,

lspci -nn | grep Eth
02:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network Connection [8086:10d3]
03:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network Connection [8086:10d3]
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)
and in ./x86_64-default-linuxapp-gcc/include/rte_pci_dev_ids.h

#define E1000_DEV_ID_I350_COPPER                0x1521
is present.
regards,
Ayon

On Thu, Jan 15, 2015 at 12:11 PM, Zhang, Helin <helin.zhang@intel.com<mailto:helin.zhang@intel.com>> wrote:
Check the device ID can know if your NIC is supported by dpdk or not.

"Lspci -nn | grep Eth" will show like below, 1521 is the device ID.
04:00.0 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521]
Then check rte_pci_dev_ids.h to see if that device ID is listed in that file or not, then you know if your NIC is supported or not.

Regards,
Helin

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org<mailto:dev-bounces@dpdk.org>] On Behalf Of ayon jyoti Biswas
> Sent: Thursday, January 15, 2015 2:29 PM
> To: dev@dpdk.org<mailto:dev@dpdk.org>
> Subject: [dpdk-dev] How to run intel dpdk apps on '82574L Gigabit Network
> Connection' NIC cards
>
> hi,
> i have two* '82574L Gigabit Network Connection'*  NIC cards .
> Can i run dpdk application with this interfaces .
> i have binded to igb_uio . My l2forward application is successfully getting
> initialized but could not receive/transmit traffic .
> How can i run dpdk l2fwd application with this NIC cards .
>
>
>
> ./build/app/l2fwd -c 0x3 -n 2 -m 512 -- -p 0x3
>
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f8bbaa00000 (size = 0x200000)
> EAL: Ask a virtual area of 0xffc00000 bytes
> EAL: Virtual area found at 0x7f8abac00000 (size = 0xffc00000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f8aba800000 (size = 0x200000)
> EAL: Requesting 256 pages of size 2MB from socket 0
> EAL: TSC frequency is ~3192736 KHz
> EAL: Master core 0 is ready (tid=bb5be800)
> EAL: Core 1 is ready (tid=b9ffe700)
> EAL: PCI device 0000:02:00.0 on NUMA socket -1
> EAL:   probe driver: 8086:10d3 rte_em_pmd
> EAL:   PCI memory mapped at 0x7f8bb95de000
> EAL:   PCI memory mapped at 0x7f8bb955e000
> EAL:   PCI memory mapped at 0x7f8bb955a000
> EAL: PCI device 0000:03:00.0 on NUMA socket -1
> EAL:   probe driver: 8086:10d3 rte_em_pmd
> EAL:   PCI memory mapped at 0x7f8bb953a000
> EAL:   PCI memory mapped at 0x7f8bb94ba000
> EAL:   PCI memory mapped at 0x7f8bb94b6000
>
> ************NUMBER OF PORTS=2**********
> Lcore 0: RX port 0
> Lcore 1: RX port 1
> Initializing port 0...
>  ***********PORTID= 0*********
>
>
> ./tools/pci_unbind.py --status
>
> Network devices using IGB_UIO driver
> ====================================
> 0000:02:00.0 '82574L Gigabit Network Connection' drv=igb_uio
> unused=e1000e
> 0000:03:00.0 '82574L Gigabit Network Connection' drv=igb_uio
> unused=e1000e
>
>
> ethtool -i eth3
> driver: e1000e
> version: 2.1.4-k
> firmware-version: 1.8-0
> bus-info: 0000:03:00.0
> supports-statistics: yes
> supports-test: yes
> supports-eeprom-access: yes
> supports-register-dump: yes
> supports-priv-flags: no
>
> ethtool -i eth4
> driver: e1000e
> version: 2.1.4-k
> firmware-version: 1.8-0
> bus-info: 0000:02:00.0
> supports-statistics: yes
> supports-test: yes
> supports-eeprom-access: yes
> supports-register-dump: yes
> supports-priv-flags: no
>
>
> thanks
> ayon


  parent reply	other threads:[~2015-01-15  7:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15  6:29 ayon jyoti Biswas
2015-01-15  6:41 ` Zhang, Helin
     [not found]   ` <CABq0x8RZmUHSqACMssXD001Za=1b2KGU2dfOZpQdchTxZRsQTA@mail.gmail.com>
2015-01-15  7:24     ` Zhang, Helin [this message]
     [not found]       ` <CABq0x8QpZZBwFtxDp9tAgJsSs7O88q9dckdJeLoheO1-utG9Nw@mail.gmail.com>
2015-01-15  7:46         ` Zhang, Helin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F35DEAC7BCE34641BA9FAC6BCA4A12E70A7E8D8B@SHSMSX104.ccr.corp.intel.com \
    --to=helin.zhang@intel.com \
    --cc=ajbiswas2009@gmail.com \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).