From: Markus Theil <markus.theil@tu-ilmenau.de>
To: "Mor, Omri" <omrimor2@illinois.edu>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Support for Intel 82579LM (8086:1502)
Date: Fri, 13 Oct 2017 18:38:15 +0200 [thread overview]
Message-ID: <ce59f564-e0d3-2a60-645f-3858d9b771ae@tu-ilmenau.de> (raw)
In-Reply-To: <48DE7D41-F1DC-4738-B7E3-9BFE6D92789C@illinois.edu>
Hi,
I wrote a little patch for you. You can apply it to the current
dpdk-master branch and test it.
My Thinkpad T430 has such a NIC and shows some rx packets and the link
status change with the patch,
when using testpmd. Maybe 82579LM was not supported for a reason, so
simply try out if it works for your purpose :)
Markus
On 12.10.2017 22:47, Mor, Omri wrote:
> Hello,
>
> I have a computer I’m using for testing DPDK that has an Intel 82579LM.
> Currently this NIC isn’t supported in DPDK, but I believe it is similar to others that are (such as the 82574L, which I am using successfully on another computer).
> How much work would be required in getting this up and running—what functionality is missing?
> I’m currently using it with AF_PACKET (and will try pcap soon), but would be interested in seeing its performance under DPDK ‘native’.
>
> Thank you,
> Omri Mor
next prev parent reply other threads:[~2017-10-13 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 20:47 Mor, Omri
2017-10-13 16:32 ` [dpdk-dev] [PATCH] net/e1000: add pci ids for 82579LM Markus Theil
2018-01-11 7:11 ` [dpdk-dev] " Wenzhuo Lu
2018-01-13 15:46 ` Zhang, Helin
2017-10-13 16:38 ` Markus Theil [this message]
2017-10-13 20:13 ` [dpdk-dev] Support for Intel 82579LM (8086:1502) Mor, Omri
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=ce59f564-e0d3-2a60-645f-3858d9b771ae@tu-ilmenau.de \
--to=markus.theil@tu-ilmenau.de \
--cc=dev@dpdk.org \
--cc=omrimor2@illinois.edu \
/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).