From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH v2 0/3] improve cmdline file handling in testpmd
Date: Fri, 4 Jul 2025 19:34:33 +0100 [thread overview]
Message-ID: <20250704183437.25901-1-bruce.richardson@intel.com> (raw)
In-Reply-To: <20250704140551.4151993-1-bruce.richardson@intel.com>
Some small improvements to cmdline file handling testpmd, inspired by the
desire to have support for multiple cmdline files passed on the commandline
of a testpmd run.
The implementation is somewhat complicated by the setting for echo/noecho
of the commands, because the current implementation uses a global flag for
that - shared between cmdline parameters and interactive CLI commands.
V2:
* remove global echo flag, and now support echo/noecho per file loaded
* when echoing, output the file being processed, to clarify things when
loading multiple files.
Bruce Richardson (3):
app/testpmd: explicitly set command echoing on file load
app/testpmd: allow multiple commandline file parameters
app/testpmd: improve output when processing cmdline files
app/test-pmd/cmdline.c | 78 ++++++++++++++++++---
app/test-pmd/parameters.c | 17 +++--
app/test-pmd/testpmd.c | 13 ++--
app/test-pmd/testpmd.h | 15 +++-
doc/guides/testpmd_app_ug/run_app.rst | 3 +-
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 12 ++--
6 files changed, 110 insertions(+), 28 deletions(-)
--
2.48.1
next prev parent reply other threads:[~2025-07-04 18:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 14:05 [PATCH] app/testpmd: allow multiple cmdline-file parameters Bruce Richardson
2025-07-04 18:34 ` Bruce Richardson [this message]
2025-07-04 18:34 ` [PATCH v2 1/3] app/testpmd: explicitly set command echoing on file load Bruce Richardson
2025-07-04 18:34 ` [PATCH v2 2/3] app/testpmd: allow multiple commandline file parameters Bruce Richardson
2025-07-04 18:34 ` [PATCH v2 3/3] app/testpmd: improve output when processing cmdline files Bruce Richardson
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=20250704183437.25901-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@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).