DPDK usage discussions
 help / color / mirror / Atom feed
From: James Bensley <jwbensley@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] DPDK support for 82579
Date: Tue, 31 Oct 2017 12:14:16 +0000	[thread overview]
Message-ID: <CAAWx_pX5tWskOZp-Az4rDS6_zATix0BOAdQtJxk0ZWP2_P5DKw@mail.gmail.com> (raw)

Hi All,

I have see the list of support NICs here: http://dpdk.org/doc/nics

Although it doesn’t say which NICs are confirmed as NOT working. I
have looking into DPDK support (for Pktgen and Moongen) on commodity
devices (e.g. laptops and desktops). I have DPDK + Pktgen compiled and
working on my home desktop:

bensley@htpc-ubuntu:/opt/dpdk/dpdk-17.08/usertools$ lspci | grep Eth
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection
I217-V (rev 05)

However on my laptop it seems the NIC is “unsupported”:

bensley@ubuntu-laptop:/opt/dpdk/dpdk-17.08/usertools$ lspci | grep Eth
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
Connection (rev 04)

When I say unsupported I mean that Intel 82579 chips aren’t on the
list of supported NICs (where as I217 is explicitly listed) so I have
two questions;

1. Is there a list of confirmed unsupported NICs?

2. It maybe that this NIC will work but it is untested (unless someone
can confirm otherwise) so is there a way I can force DPDK + Pktgen to
try and use this 82579 NIC?

Please see this output of me trying to bind the laptop NIC to DPDK,
dpdk-devbind.py doesn't explicitly reject the NIC (by which I mean no
error message and the return code from `sudo ./dpdk-devbind.py -b
e1000e 00:19.0` is 0) but it simply doesn’t work, the NIC is “given”
back to the Kernel:
https://null.53bits.co.uk/uploads/linux/applications/dpdk/Ubuntu-Laptop-DPDK-NIC-Bind.txt

In the `lshw` output it can be seen that the NIC uses an e1000e
driver, do I need to compile the e1000e driver bundled with the DPDK
source and replace my existing/native driver with that, if so how can
I compile it?

bensley@ubuntu-laptop:/opt/dpdk/dpdk-17.08/drivers/net/e1000$ make
Makefile:32: /mk/rte.vars.mk: No such file or directory
Makefile:103: /mk/rte.lib.mk: No such file or directory
make: *** No rule to make target '/mk/rte.lib.mk'. Stop.

Cheers,
James.

P.S. I’m using DPDK 17.08 and Pktgen 3.4.2, I did a vanilla compile,
using these exact commands:
https://null.53bits.co.uk/index.php?page=ptkgen-install

             reply	other threads:[~2017-10-31 12:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 12:14 James Bensley [this message]
2017-10-31 21:50 ` Stephen Hemminger
2017-11-01 21:11   ` James Bensley
2017-11-02  7:31     ` Stephen Hemminger

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=CAAWx_pX5tWskOZp-Az4rDS6_zATix0BOAdQtJxk0ZWP2_P5DKw@mail.gmail.com \
    --to=jwbensley@gmail.com \
    --cc=users@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).