From: Mikael R Carlsson <mikael.r.carlsson@tietoevry.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Relation between DPDK queue and descriptors
Date: Wed, 2 Oct 2024 15:21:45 +0000 [thread overview]
Message-ID: <AS8PR04MB819947FB6CC8EBA3A544388FA6702@AS8PR04MB8199.eurprd04.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 495 bytes --]
Hi experts!
I have a hard time to finds a good documentation about the relation between DPDK TX queue and descriptors.
Queue as in rte_eth_tx_queue_setup
Descriptor as in rte_eth_dev_adjust_nb_rx_rx_desc
We suspect we run out of descriptors in TX path, we are not sure here. We use more than one TX queue. Will we get more descriptors if we only use one single TX queue? Does anyone know if there is some good documentation regarding the TX queue and the descriptors?
/ Mikael
[-- Attachment #2: Type: text/html, Size: 2385 bytes --]
next reply other threads:[~2024-10-02 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 15:21 Mikael R Carlsson [this message]
2024-10-02 15:29 ` Stephen Hemminger
2024-10-02 16:04 ` Mikael R Carlsson
2024-10-02 16:07 ` Pathak, Pravin
2024-10-03 7:37 ` Mikael R Carlsson
2024-10-03 8:34 ` Dmitry Kozlyuk
2024-10-03 15:20 ` Stephen Hemminger
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=AS8PR04MB819947FB6CC8EBA3A544388FA6702@AS8PR04MB8199.eurprd04.prod.outlook.com \
--to=mikael.r.carlsson@tietoevry.com \
--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).