DPDK usage discussions
 help / color / mirror / Atom feed
From: Mikael R Carlsson <mikael.r.carlsson@tietoevry.com>
To: "Pathak, Pravin" <pravin.pathak@intel.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: RE: Relation between DPDK queue and descriptors
Date: Thu, 3 Oct 2024 07:37:34 +0000	[thread overview]
Message-ID: <AS8PR04MB81991E6E19F9627070AB8517A6712@AS8PR04MB8199.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <BL1PR11MB54616662499343A3574615C4F4702@BL1PR11MB5461.namprd11.prod.outlook.com>

Hi!

Thanks. 

According to chatgpt the descriptors are shared over all TX queues. 

So, in a 4 TX queue and 1024 descriptors scenario I would be able to get maximum 256 descriptors per TX queue (If I want same amount on all queues). But if I only used 1 TX queue, I would get all 1024 descriptors on that single TX queue.

  / Mikael




-----Original Message-----
From: Pathak, Pravin <pravin.pathak@intel.com> 
Sent: Wednesday, October 2, 2024 6:07 PM
To: Mikael R Carlsson <mikael.r.carlsson@tietoevry.com>; Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: RE: Relation between DPDK queue and descriptors

[Du f?r inte e-post ofta fr?n pravin.pathak@intel.com. L?s om varf?r det h?r ?r viktigt p? https://aka.ms/LearnAboutSenderIdentification ]

Hi Mikael -
ChatGpt provides a good description of the relation between these two. If you ask ChatGPT to do a deep dive, it will provide a good bit of programming and optimization details.
Regards
Pravin


> -----Original Message-----
> From: Mikael R Carlsson <mikael.r.carlsson@tietoevry.com>
> Sent: Wednesday, October 2, 2024 12:05 PM
> To: Stephen Hemminger <stephen@networkplumber.org>
> Cc: users@dpdk.org
> Subject: RE: Relation between DPDK queue and descriptors
>
> Hi!
>
> Thanks for the response.
>
> I think I get the descriptor part, but what is the relation to queues? 
> If the hardware supports 1024 descriptors and I need 6 queues, do I 
> have 1024 descriptors on each TX queue?
>
>   / Mikael
>
>
> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Wednesday, October 2, 2024 5:29 PM
> To: Mikael R Carlsson <mikael.r.carlsson@tietoevry.com>
> Cc: users@dpdk.org
> Subject: Re: Relation between DPDK queue and descriptors
>
> On Wed, 2 Oct 2024 15:21:45 +0000
> Mikael R Carlsson <mikael.r.carlsson@tietoevry.com> wrote:
>
> > 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
> >
>
> A typical driver has a hardware ring buffer between the driver and the 
> hardware.
> One ring for transmit, and another for receive.
> The entries in the ring are hardware specific data structure called descriptors.
> Each descriptor usually has physical memory address, size, and flags.
>
> The number of Rx descriptors determines the number of unread frames 
> the driver can hold. Too small, and you risk dropping packets; too 
> large and under stress load the driver can end up buffering 
> excessively causing latency (bufferbloat).
> Similar on Tx but less of a problem because typically the network is 
> faster than the application can send packets.

  reply	other threads:[~2024-10-03  7:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 15:21 Mikael R Carlsson
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 [this message]
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=AS8PR04MB81991E6E19F9627070AB8517A6712@AS8PR04MB8199.eurprd04.prod.outlook.com \
    --to=mikael.r.carlsson@tietoevry.com \
    --cc=pravin.pathak@intel.com \
    --cc=stephen@networkplumber.org \
    --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).