From: Bruce Richardson <bruce.richardson@intel.com>
To: tom.barbette@ulg.ac.be
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] No packets received if burst is too small in rte_eth_rx_burst
Date: Wed, 14 Dec 2016 16:52:21 +0000 [thread overview]
Message-ID: <20161214165220.GC110884@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <597694261.17905196.1481728433903.JavaMail.zimbra@ulg.ac.be>
On Wed, Dec 14, 2016 at 04:13:53PM +0100, tom.barbette@ulg.ac.be wrote:
> Hi list,
>
> Between 2.2.0 and 16.04 (up to at least 16.07.2 if not current), with the XL710 controller I do not get any packet when calling rte_eth_rx_burst if nb_pkts is too small. I would say smaller than 32. The input rate is not big, if that helps. But It should definitely get at least one packet per second.
>
> Any ideas? Is that a bug or expected behaviour? Could be caused by other ABI changes?
>
Does this issue still occur even if you disable the vector driver in
your build-time configuration?
/Bruce
next prev parent reply other threads:[~2016-12-14 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <415214732.17903310.1481728244157.JavaMail.zimbra@ulg.ac.be>
2016-12-14 15:13 ` tom.barbette
2016-12-14 16:52 ` Bruce Richardson [this message]
2016-12-17 10:43 ` tom.barbette
2016-12-19 10:25 ` Bruce Richardson
2016-12-19 13:24 ` Thomas Monjalon
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=20161214165220.GC110884@bricha3-MOBL3.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=tom.barbette@ulg.ac.be \
/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).