From: Stephen Hemminger <stephen@networkplumber.org>
To: Antonio Di Bacco <a.dibacco.ks@gmail.com>
Cc: "Gábor LENCSE" <lencse@hit.bme.hu>, users@dpdk.org
Subject: Re: rte_eth_tx_burst() always returns 0 in tight loop
Date: Mon, 26 Sep 2022 10:24:07 -0700 [thread overview]
Message-ID: <20220926102407.021f6820@hermes.local> (raw)
In-Reply-To: <CAO8pfFkmzbYrPLRnbEh8iqM8WCL_Y_8xYhB8e3XH_+GJyW+k8g@mail.gmail.com>
On Mon, 26 Sep 2022 17:36:06 +0200
Antonio Di Bacco <a.dibacco.ks@gmail.com> wrote:
> Is there any way to check if a TX queue is full before transmitting
> using the rte_eth_rx_burst() or should I rely on the return value of
> rte_eth_tx_burst()?
There is an API that might help rte_eth_tx_descriptor_status
but only some drivers support it. And it requires some detailed knowledge
about which descriptor is being used.
next prev parent reply other threads:[~2022-09-26 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 15:57 Antonio Di Bacco
2022-07-03 20:18 ` Gábor LENCSE
2022-07-06 7:21 ` Antonio Di Bacco
2022-07-06 15:00 ` Stephen Hemminger
2022-07-07 14:30 ` Antonio Di Bacco
2022-09-26 15:36 ` Antonio Di Bacco
2022-09-26 17:24 ` Stephen Hemminger [this message]
2022-07-06 15:03 ` Gábor LENCSE
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=20220926102407.021f6820@hermes.local \
--to=stephen@networkplumber.org \
--cc=a.dibacco.ks@gmail.com \
--cc=lencse@hit.bme.hu \
--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 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).