From: Masoud Moshref Javadi <masood.moshref.j@gmail.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Subject: [dts] The semantics of rte_eth_rx_burst and rte_eth_rx_queue_count
Date: Mon, 27 Jul 2015 11:04:14 -0700 [thread overview]
Message-ID: <55B6729E.60104@gmail.com> (raw)
Hi,
I don't understand the semantics of these two methods (rte_eth_rx_burst
and rte_eth_rx_queue_count).
For rte_eth_rx_burst with burst of B.
* Does that mean it will not return until it receive at least B
packets? or it just returns with whatever packets that are in the
NIC's queue?
* Does that mean it will wait at least x clocks before returning 0 to
B packets?
For rte_eth_rx_queue_count:
* Does it go to the NIC and poll the # filled entries at its queue? if
yes, how much is its overhead?
* Do we need to call rte_eth_rx_burst (or similar methods) to make it
updated?
Regards
next reply other threads:[~2015-07-27 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 18:04 Masoud Moshref Javadi [this message]
2015-07-27 22:47 ` Masoud Moshref Javadi
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=55B6729E.60104@gmail.com \
--to=masood.moshref.j@gmail.com \
--cc=dts@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).