DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: Mikael R Carlsson <mikael.r.carlsson@tietoevry.com>,
	"Pathak, Pravin" <pravin.pathak@intel.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: Relation between DPDK queue and descriptors
Date: Thu, 3 Oct 2024 08:20:33 -0700	[thread overview]
Message-ID: <20241003082033.48d44016@hermes.local> (raw)
In-Reply-To: <20241003113436.2dc280e7@sovereign>

On Thu, 3 Oct 2024 11:34:36 +0300
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com> wrote:

> 2024-10-03 07:37 (UTC+0000), Mikael R Carlsson:
> > 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.  
> 
> This is not so, ChatGPT errs.
> The number of advertised and configured descriptors is per queue
> (the latter is per the specific queue being configured, actually).
> You won't get more descriptors per queue if you use fewer queues.
> Note, however, that queues consume NIC resources and larger queues stress
> CPU cache, so it is not always the best to have many queues or large queues.

Also, large numbers of descriptors means the mbuf pool much be larger which can exhaust
the available huge page memory.  If you had 4 Tx queue * 1024 descriptors per queue
the Tx side could consume as much as 4K * 2K  = 8 Meg of hugepage memory.
And on Rx side same applies.

      reply	other threads:[~2024-10-03 15:20 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
2024-10-03  8:34         ` Dmitry Kozlyuk
2024-10-03 15:20           ` Stephen Hemminger [this message]

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=20241003082033.48d44016@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=mikael.r.carlsson@tietoevry.com \
    --cc=pravin.pathak@intel.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).