From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Helmut Sim <simhelmut-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: eth dev doesn't free mbufs for 82575EB
Date: Wed, 11 Jun 2014 18:18:59 +0200 [thread overview]
Message-ID: <1879872.RfA1LW5PMu@xps13> (raw)
In-Reply-To: <CAF8yGaEdHvJOGHK4P8tH5vYsVSgYX8Wob5E7xAKwGGyMn=BKQA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-30 15:44, Helmut Sim:
> I am trying to verify that the 82575EB NIC functions well.
> The file rte_pci_dev_ids.h includes the following lines:
>
> #ifdef RTE_PCI_DEV_USE_82575EB_COPPER
> RTE_PCI_DEV_ID_DECL_IGB(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82575EB_COPPER)
> #endif
>
> so I defined the RTE_PCI_DEV_USE_82575EB_COPPER and hoped it will work well.
This commit could interest you:
http://dpdk.org/browse/dpdk/commit/?id=cc333208d5658fea6420
--
Thomas
next prev parent reply other threads:[~2014-06-11 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 12:44 eth dev doesn't free mbufs for 82575EB Helmut Sim
[not found] ` <CAF8yGaEdHvJOGHK4P8tH5vYsVSgYX8Wob5E7xAKwGGyMn=BKQA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-11 16:18 ` Thomas Monjalon [this message]
2014-06-19 14:02 ` Helmut Sim
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=1879872.RfA1LW5PMu@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=simhelmut-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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