From: Prashant Upadhyaya <praupadhyaya@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Regarding rte_eth_rx_burst
Date: Sun, 10 May 2020 19:35:52 +0530 [thread overview]
Message-ID: <CAPBAu3W=-P5LrmzgZAk8Xi=JOLvHET7A-BPDae7riofd8P-BZA@mail.gmail.com> (raw)
Hi,
I recently started using X722 NIC which uses i40 PMD of DPDK.
I am on DPDK 20.02.
I am seeing that when I call the rte_eth_rx_burst with last argument
as 1 (polling for 1 mbuf), then I am not receiving data via repeated
calls.
When I go for calls to rte_eth_rx_burst with last argument as 32, the
function does return the mbuf's as received data.
Is this expected ? Or this is a bug in the i40 driver handling this NIC ?
The polls to rte_eth_rx_burst with last argument as 1 works well for
the ixgbe PMD for sure since I have been using X520 successfully with
last argument as 1.
Regards
-Prashant
next reply other threads:[~2020-05-10 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 14:05 Prashant Upadhyaya [this message]
2020-05-10 17:16 ` Wang, Haiyue
2020-05-11 5:58 ` Prashant Upadhyaya
2020-05-11 6:28 ` Wang, Haiyue
2020-05-11 8:31 ` Prashant Upadhyaya
2020-05-11 8:40 ` Wang, Haiyue
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='CAPBAu3W=-P5LrmzgZAk8Xi=JOLvHET7A-BPDae7riofd8P-BZA@mail.gmail.com' \
--to=praupadhyaya@gmail.com \
--cc=dev@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).