DPDK patches and discussions
 help / color / mirror / Atom feed
From: Doug Foster <doug.foster@arm.com>
To: dev@dpdk.org
Cc: nd@arm.com, Doug Foster <doug.foster@arm.com>
Subject: [PATCH 0/2] app/test-pipeline: cleanup and add ring/help options
Date: Tue,  4 Nov 2025 02:49:17 +0000	[thread overview]
Message-ID: <20251104024919.3329372-1-doug.foster@arm.com> (raw)

This patchset adds command-line options to configure the size of RX and
TX rings in the test-pipeline application. The current implementation
fixes the ring size at 128, which cannot be changed through the command
line. This default value may not be optimal, as the ideal ring size
depends on the platform and the CPU's ability to process entries before
they are dequeued.

This was confirmed by the observation of 66% failed enqueue attempts to
the RX ring on the Grace CPU when using a ring size of 128, indicating
that the ring was too small for the workload. Increasing the RX ring
size to 256 reduced the number of failed enqueue attempts to 22% and
improved overall throughput by approximately 22%.

In addition to making the ring sizes configurable, this patchset
introduces a help option to make valid parameters easier to understand.
It also includes minor cleanup to improve readability and
maintainability of the code.

Doug Foster (2):
  app/test-pipeline: cleanup and add help
  app/test-pipeline: add ring size options

 app/test-pipeline/config.c                 | 131 +++++++++++++++------
 app/test-pipeline/init.c                   |   4 -
 app/test-pipeline/main.h                   |   9 +-
 doc/guides/sample_app_ug/test_pipeline.rst |  12 +-
 4 files changed, 114 insertions(+), 42 deletions(-)

-- 
2.34.1


             reply	other threads:[~2025-11-04  2:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04  2:49 Doug Foster [this message]
2025-11-04  2:49 ` [PATCH 1/2] app/test-pipeline: cleanup and add help Doug Foster
2025-11-04  2:49 ` [PATCH 2/2] app/test-pipeline: add ring size options Doug Foster

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=20251104024919.3329372-1-doug.foster@arm.com \
    --to=doug.foster@arm.com \
    --cc=dev@dpdk.org \
    --cc=nd@arm.com \
    /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).