All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lavanya Jose <lavanya.jose@gmail.com>
To: users@dpdk.org, dev@dpdk.org
Subject: rte_eth_rx bug? duplicate message bufs
Date: Mon, 8 Aug 2016 11:44:00 -0700	[thread overview]
Message-ID: <CADi0TLcpWMhcDnXX9qczOA8Usz7M+NUZriS0znuVj1d=S23mFQ@mail.gmail.com> (raw)

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-08 18:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-08 18:44 Lavanya Jose [this message]
2016-08-11 23:53 ` rte_eth_rx bug? duplicate message bufs Yeddula, Avinash
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='CADi0TLcpWMhcDnXX9qczOA8Usz7M+NUZriS0znuVj1d=S23mFQ@mail.gmail.com' \
    --to=lavanya.jose@gmail.com \
    --cc=dev@dpdk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.