From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Wei Zhao" <wei.zhao1@intel.com>, "Jeff Guo" <jia.guo@intel.com>
Cc: <dev@dpdk.org>, "Thomas Monjalon" <thomas@monjalon.net>,
"Ferruh Yigit" <ferruh.yigit@intel.com>,
"Andrew Rybchenko" <arybchenko@solarflare.com>
Subject: [dpdk-dev] ixgbe vector rx does not conform to rte_eth_rx_burst() API
Date: Wed, 15 Jul 2020 18:02:50 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35C61127@smartserver.smartshare.dk> (raw)
Wei, Jeff,
For the ixgbe driver using vector functions, i.e. ixgbe_recv_pkts_vec(), calling rte_eth_rx_burst() with nb_pkts > RTE_IXGBE_MAX_RX_BURST only returns RTE_IXGBE_MAX_RX_BURST packets. E.g. calling rte_eth_rx_burst() with nb_pkts=64 only returns 32 packets.
The API description of rte_eth_rx_burst() says:
<quote>
The rte_eth_rx_burst() function returns the number of packets actually retrieved, which is the number of rte_mbuf data structures effectively supplied into the rx_pkts array. A return value equal to nb_pkts indicates that the RX queue contained at least rx_pkts packets, and this is likely to signify that other received packets remain in the input queue. Applications implementing a "retrieve as much received packets as possible" policy can check this specific case and keep invoking the rte_eth_rx_burst() function until a value less than nb_pkts is returned.
</quote>
The driver implementation does not conform to the documented behavior for "retrieve as much received packets as possible" applications.
Med venlig hilsen / kind regards
- Morten Brørup
next reply other threads:[~2020-07-15 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 16:02 Morten Brørup [this message]
2020-07-16 8:49 ` Zhao1, Wei
2020-07-16 9:08 ` [dpdk-dev] ixgbe vector rx does not conform torte_eth_rx_burst() API Morten Brørup
2020-07-17 13:49 ` Bruce Richardson
2020-07-18 3:32 ` Zhao1, Wei
2020-07-18 3:44 ` Zhao1, Wei
2020-07-27 9:42 ` [dpdk-dev] ixgbe vector rx does not conform to rte_eth_rx_burst() API Morten Brørup
2020-07-27 10:35 ` Zhao1, Wei
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=98CBD80474FA8B44BF855DF32C47DC35C61127@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jia.guo@intel.com \
--cc=thomas@monjalon.net \
--cc=wei.zhao1@intel.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).