From: Helmut Sim <simhelmut@gmail.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] eth dev doesn't free mbufs for 82575EB
Date: Thu, 19 Jun 2014 17:02:24 +0300 [thread overview]
Message-ID: <CAF8yGaFbecGyFdrCKA++ENjaOxHvkzm5x3YXxYFOf9E-v4WkNg@mail.gmail.com> (raw)
In-Reply-To: <1879872.RfA1LW5PMu@xps13>
Thanks,
it has the same effect as my changeee
i found the lost packets issue... it was related to my app implementation
(a bug with increasing the number of segments at the nb_segs variable).
anyway thanks.
On Wed, Jun 11, 2014 at 7:18 PM, Thomas Monjalon <thomas.monjalon@6wind.com>
wrote:
> 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
>
prev parent reply other threads:[~2014-06-19 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 12:44 Helmut Sim
2014-06-11 16:18 ` Thomas Monjalon
2014-06-19 14:02 ` Helmut Sim [this message]
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=CAF8yGaFbecGyFdrCKA++ENjaOxHvkzm5x3YXxYFOf9E-v4WkNg@mail.gmail.com \
--to=simhelmut@gmail.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).