From: James Bensley <jwbensley@gmail.com>
To: users@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [dpdk-users] DPDK support for 82579
Date: Wed, 1 Nov 2017 21:11:09 +0000 [thread overview]
Message-ID: <CAAWx_pVufBxevQtzSGKHzmjX_McLQL92j-Qc8oqRHGRQ45-B3w@mail.gmail.com> (raw)
In-Reply-To: <20171031225048.34120581@shemminger-XPS-13-9360>
On 31 October 2017 at 21:50, Stephen Hemminger
<stephen@networkplumber.org> wrote:
> First off, I assume the device works for normal Linux networking.
> Then check the PCI-id value for the device and see if it is present in drivers/net/e1000
> in DPDK. If not, then it maybe as simple as adding the necessary ID value to the
> table. Also, check current git.
>
> It maybe more complex where some PHY code has to be backported from
> BSD into DPDK. Unfortunately, the device support in DPDK lags behind Linux
> and BSD. There are many variants and even Intel doesn't have resources to
> keep DPDK up to all the current PCI id values.
Hi Stephen,
That has worked! Yes this is a working NIC built into a laptop.
bensley@ubuntu-laptop:/opt/dpdk/dpdk-17.08/drivers/net/e1000$ lspci
-nn | grep Eth
00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit
Network Connection [8086:1502] (rev 04)
bensley@ubuntu-laptop:/opt/dpdk/dpdk-17.08/drivers/net/e1000$ grep -r 1502 *
base/e1000_hw.h:#define E1000_DEV_ID_PCH2_LV_LM 0x1502
^ This PCI-id is alread "known" but not mapped to the driver so I just
added the two lines to em_ethdev.c below, recompiled DPDK and Pktgen
and it works...
bensley@ubuntu-laptop:/opt/dpdk/dpdk-17.08/drivers/net/e1000$ grep -r
E1000_DEV_ID_PCH2_LV_LM *
base/e1000_hw.h:#define E1000_DEV_ID_PCH2_LV_LM 0x1502
base/e1000_api.c: case E1000_DEV_ID_PCH2_LV_LM:
em_ethdev.c: { RTE_PCI_DEVICE(E1000_INTEL_VENDOR_ID,
E1000_DEV_ID_PCH2_LV_LM) },
em_ethdev.c: case E1000_DEV_ID_PCH2_LV_LM:
Thanks very much for your help!
Cheers,
James.
next prev parent reply other threads:[~2017-11-01 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 12:14 James Bensley
2017-10-31 21:50 ` Stephen Hemminger
2017-11-01 21:11 ` James Bensley [this message]
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_pVufBxevQtzSGKHzmjX_McLQL92j-Qc8oqRHGRQ45-B3w@mail.gmail.com \
--to=jwbensley@gmail.com \
--cc=stephen@networkplumber.org \
--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).