DPDK patches and discussions
 help / color / mirror / Atom feed
From: Chetan Bali <chetan.bali@aricent.com>
To: "Jayakumar, Muthurajan" <muthurajan.jayakumar@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Intel 82571EB PMD support
Date: Sun, 9 Mar 2014 11:28:48 +0530	[thread overview]
Message-ID: <8E6973B6CEA617469C62E4FDA1670F0631B10809B0@GUREXMB01.ASIAN.AD.ARICENT.COM> (raw)
In-Reply-To: <5D695A7F6F10504DBD9B9187395A21797C6EDB13@ORSMSX103.amr.corp.intel.com>

Hi,
Have checked this file too. It's listed and also init of pmd is fine and working since link is up.

After sending the packets from directly connected interface, we are seeing that rx nic stats are increasing but
We are not seeing descriptor done status ( E1000_RX_STAT_DD ) set hence it is not able to get the packet from rx software ring.

Since the link is up, it should be able to receive the packets. Can anyone help resolve this issue?

Thanks & Regards
Chetan Bali
________________________________________
From: Jayakumar, Muthurajan [muthurajan.jayakumar@intel.com]
Sent: Saturday, March 08, 2014 9:52 PM
To: Chetan Bali; dev@dpdk.org
Subject: RE: Intel 82571EB PMD support

Hi Chetan,

82571EB is supported  - listed in http://dpdk.org/browse/dpdk/tree/lib/librte_eal/common/include/rte_pci_dev_ids.h

Not heard issue before.

RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82571EB_COPPER)
RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82571EB_FIBER)
RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82571EB_SERDES)
RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82571EB_SERDES_DUAL)
RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82571EB_SERDES_QUAD)
RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82571EB_QUAD_COPPER)


#define E1000_DEV_ID_82571EB_COPPER           0x105E
#define E1000_DEV_ID_82571EB_FIBER            0x105F
#define E1000_DEV_ID_82571EB_SERDES           0x1060
#define E1000_DEV_ID_82571EB_SERDES_DUAL      0x10D9
#define E1000_DEV_ID_82571EB_SERDES_QUAD      0x10DA
#define E1000_DEV_ID_82571EB_QUAD_COPPER      0x10A4

Thanks,

-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Chetan Bali
Sent: Saturday, March 08, 2014 4:58 AM
To: dev@dpdk.org
Subject: Re: [dpdk-dev] Intel 82571EB PMD support

Hi,

 anyone faced the same issue before?

Thanks & Regards
Chetan Bali
________________________________________
From: dev [dev-bounces@dpdk.org] On Behalf Of Chetan Bali
Sent: Friday, March 07, 2014 3:48 PM
To: dev@dpdk.org
Subject: [dpdk-dev] Intel 82571EB PMD support

Hi,

Do we have PMD support for intel 82571EB. We are having e1000e driver supported for 82571EB in linux.

DPDK Version : 1.6.0-r1

Linux Kernel : CentOS 6.4 [ kernel version 2.6.32-358.el6.x86_64 ]


Issue:

When we run DPDK example [ l2fwd ], we are able to see successful init of rte_pmd_em and link is also detected successfully.
But the RX, TX count are zero. If we try to fetch nic stats using rte_eth_stats_get(), we can see around 256 ipacket count but after that error count [rx error ] starts increasing.

We are not able to see any packet on user app [ l2fwd ]. Does anyone else face the same issue?

Regards
Chetan Bali




===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================




===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================




===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================

  reply	other threads:[~2014-03-09  6:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07 10:18 Chetan Bali
2014-03-08 12:57 ` Chetan Bali
2014-03-08 16:22   ` Jayakumar, Muthurajan
2014-03-09  5:58     ` Chetan Bali [this message]
2014-03-09 14:09 ` Stefan Baranoff
2014-03-09 14:18   ` Chetan Bali
2014-03-10 11:24     ` Chetan Bali

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=8E6973B6CEA617469C62E4FDA1670F0631B10809B0@GUREXMB01.ASIAN.AD.ARICENT.COM \
    --to=chetan.bali@aricent.com \
    --cc=dev@dpdk.org \
    --cc=muthurajan.jayakumar@intel.com \
    /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).