DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Yeddula, Avinash" <ayeddula@ciena.com>
To: Lavanya Jose <lavanya.jose@gmail.com>,
	"users@dpdk.org" <users@dpdk.org>,  "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] rte_eth_rx bug? duplicate message bufs
Date: Thu, 11 Aug 2016 19:53:25 -0400	[thread overview]
Message-ID: <A1E50D8AD6310E47A6C10F075AEDC02203961C45AA@ONWVEXCHMB01.ciena.com> (raw)
In-Reply-To: <CADi0TLcpWMhcDnXX9qczOA8Usz7M+NUZriS0znuVj1d=S23mFQ@mail.gmail.com>

Hi All,
I do have a similar issue, any response to the below email might help me as well.

Thanks
-Avinash

-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Lavanya Jose
Sent: Monday, August 08, 2016 11:44 AM
To: users@dpdk.org; dev@dpdk.org
Subject: [dpdk-dev] rte_eth_rx bug? duplicate message bufs

Hi,

I was wondering if anyone on this list has come across this problem of rte_eth_rx_burst returning the same mbuf contents multiple times especially during congestion. I notice this problem after some number of calls to rte_eth_rx_burst when I set the nb_pkts argument to anything more than 5. I did confirm that the contents (random payloads) in the duplicate packets are identical.

I looked at the corresponding ixgbe driver code that gets packets from the rx ring.
<https://github.com/emmericp/dpdk/blob/e5b112e4c7a4d63f3131294e9611e4a892b75008/drivers/net/ixgbe/ixgbe_rxtx.c#L1595>
It looks like the driver doesn't drop packets if an mbuf allocation fails.
I'm not sure if this is the root cause of the bug I'm seeing?

I'm also curious about whether I need to set rx_descs and tx_descs to 40 when I'm setting up the Intel 82599 device? The datasheet says there's 40 descriptors per TX queue though default values I've seen in code are much larger..

Thanks,
Lavanya

  reply	other threads:[~2016-08-11 23:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-08 18:44 Lavanya Jose
2016-08-11 23:53 ` Yeddula, Avinash [this message]
2016-08-11 23:57   ` Lavanya Jose

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=A1E50D8AD6310E47A6C10F075AEDC02203961C45AA@ONWVEXCHMB01.ciena.com \
    --to=ayeddula@ciena.com \
    --cc=dev@dpdk.org \
    --cc=lavanya.jose@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).