From: Bruce Richardson <bruce.richardson@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: <dev@dpdk.org>, Tyler Retzlaff <roretzla@linux.microsoft.com>,
"Thomas Monjalon" <thomas@monjalon.net>
Subject: Re: [PATCH v3 5/9] eal: define the EAL parameters in argparse format
Date: Mon, 21 Jul 2025 10:05:23 +0100 [thread overview]
Message-ID: <aH4C06sBOa7q_tlg@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <CAJFAV8y5_O3T6hLbZov0LqhXyAu2s_n0P3C3Y+WSGVUjd8gbtg@mail.gmail.com>
On Mon, Jul 21, 2025 at 10:41:33AM +0200, David Marchand wrote:
> On Fri, Jul 18, 2025 at 4:34 PM Bruce Richardson
> <bruce.richardson@intel.com> wrote:
> > +struct eal_init_args {
> > + /* define a struct member for each EAL option, member name is the same as option name.
> > + * Parameters that take an argument e.g. -l, are char *,
> > + * parameters that take no options e.g. --no-huge, are bool.
> > + * parameters that can be given multiple times e.g. -a, are arg_lists,
> > + * parameters that are optional e.g. --huge-unlink,
> > + * are char * but are set to (void *)1 if the parameter is not given.
> > + * NOTE: List is to be kept alphabetically by option name
> > + */
>
> We will have to be careful to keep this struct below, in sync with the
> options list.
> Could we construct (at build time) this structure via the options list?
>
> The rules above would be enforced at the same time.
>
> (macros + #ifdef for Linux/FreeBSD may be an issue for MSVC though...)
>
I wonder how much an issue keeping them in sync would actually be? When
adding a new option to the options list, it takes a reference to the struct
field, meaning that we can't forget to add an entry here when adding the
option. If we add here but forget to add to the options list, then obvious
the option just doesn't get parsed so testing quickly would show up the
issue.
I suppose the main concern would be around renaming or deleting options -
though in the latter case having an extra stray element in the struct isn't
a big deal.
I might have a shot at auto-generating the struct, but I'm not convinced
the complexity will be worth the benefit.
/Bruce
> > + struct arg_list allow;
> > + char *base_virtaddr;
> > + struct arg_list block;
> > + char *coremask;
> > + bool create_uio_dev;
> > + struct arg_list driver_path;
> > + char *file_prefix;
> > + char *force_max_simd_bitwidth;
> > + char *huge_dir;
> > + char *huge_unlink; /* parameter optional */
> > + char *huge_worker_stack; /* parameter optional */
> > + bool in_memory;
> > + char *iova_mode;
> > + char *lcores;
> > + bool legacy_mem;
> > + char *log_color; /* parameter optional */
> > + char *log_level;
> > + char *log_timestamp; /* parameter optional */
> > + char *main_lcore;
> > + bool match_allocations;
> > + char *mbuf_pool_ops_name;
> > + char *memory_channels;
> > + char *memory_ranks;
> > + char *memory_size;
> > + bool no_hpet;
> > + bool no_huge;
> > + bool no_pci;
> > + bool no_shconf;
> > + bool no_telemetry;
> > + char *numa_mem;
> > + char *numa_limit;
> > + char *proc_type;
> > + char *service_coremask;
> > + char *service_corelist;
> > + bool single_file_segments;
> > + char *syslog; /* parameter optional */
> > + bool telemetry;
> > + char *trace;
> > + char *trace_bufsz;
> > + char *trace_dir;
> > + char *trace_mode;
> > + struct arg_list vdev;
> > + bool version;
> > + char *vfio_intr;
> > + char *vfio_vf_token;
> > + bool vmware_tsc_map;
> > +};
> > +struct eal_init_args args;
> > +
>
> [snip]
>
> > +
> > +struct rte_argparse eal_argparse = {
> > + .prog_name = "",
> > + .usage = "<DPDK EAL options>",
> > + .epilog = "For more information on EAL options, see the DPDK documentation at: \n"
> > + "\thttps://doc.dpdk.org/guides/" RTE_EXEC_ENV_NAME "_gsg/",
>
> Options don't change that often, but I would prefer we point at the
> right release doc, rather than origin/main.
>
> diff --git a/config/meson.build b/config/meson.build
> index 40f33816aa..c3c054bae9 100644
> --- a/config/meson.build
> +++ b/config/meson.build
> @@ -70,6 +70,7 @@ abi_version = run_command(find_program('cat',
> 'more'), abi_version_file,
> so_version = abi_version.split('.')[0]
>
> # extract all version information into the build configuration
> +dpdk_conf.set('RTE_VER_MAJOR', major_version)
> dpdk_conf.set('RTE_VER_YEAR', pver.get(0).to_int())
> dpdk_conf.set('RTE_VER_MONTH', pver.get(1).to_int())
> if pver.get(2).contains('-rc')
> diff --git a/lib/eal/common/eal_common_options.c
> b/lib/eal/common/eal_common_options.c
> index 787f759196..e11d76589f 100644
> --- a/lib/eal/common/eal_common_options.c
> +++ b/lib/eal/common/eal_common_options.c
> @@ -196,7 +196,11 @@ struct rte_argparse eal_argparse = {
> .prog_name = "",
> .usage = "<DPDK EAL options>",
> .epilog = "For more information on EAL options, see the DPDK
> documentation at: \n"
> +#ifdef RTE_VER_RELEASE == 99
> +
> "\thttps://doc.dpdk.org/guides-"RTE_STR(RTE_VER_MAJOR)"/"
> RTE_EXEC_ENV_NAME "_gsg/",
> +#else
> "\thttps://doc.dpdk.org/guides/"
> RTE_EXEC_ENV_NAME "_gsg/",
> +#endif
> .exit_on_error = true,
> .callback = arg_list_callback,
> .print_help = eal_usage,
>
>
> --
> David Marchand
>
next prev parent reply other threads:[~2025-07-21 9:06 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 16:40 [RFC PATCH 0/7] rework EAL argument parsing in DPDK Bruce Richardson
2025-05-20 16:40 ` [RFC PATCH 1/7] eal: add long options for each short option Bruce Richardson
2025-05-20 16:40 ` [RFC PATCH 2/7] argparse: add support for string and boolean args Bruce Richardson
2025-05-20 16:40 ` [RFC PATCH 3/7] argparse: make argparse EAL-args compatible Bruce Richardson
2025-05-22 10:44 ` Bruce Richardson
2025-05-20 16:40 ` [RFC PATCH 4/7] eal: define the EAL parameters in argparse format Bruce Richardson
2025-05-20 16:40 ` [RFC PATCH 5/7] eal: gather EAL args before processing Bruce Richardson
2025-05-20 16:40 ` [RFC PATCH 6/7] eal: combine parameter validation checks Bruce Richardson
2025-05-20 16:40 ` [RFC PATCH 7/7] eal: simplify handling of conflicting cmdline options Bruce Richardson
2025-07-08 17:20 ` [RFC PATCH v2 0/5] rework EAL argument parsing in DPDK Bruce Richardson
2025-07-08 17:20 ` [RFC PATCH v2 1/5] eal: add long options for each short option Bruce Richardson
2025-07-08 17:20 ` [RFC PATCH v2 2/5] eal: define the EAL parameters in argparse format Bruce Richardson
2025-07-08 17:20 ` [RFC PATCH v2 3/5] eal: gather EAL args before processing Bruce Richardson
2025-07-08 17:20 ` [RFC PATCH v2 4/5] eal: combine parameter validation checks Bruce Richardson
2025-07-08 17:20 ` [RFC PATCH v2 5/5] eal: simplify handling of conflicting cmdline options Bruce Richardson
2025-07-08 18:41 ` [RFC PATCH v2 0/5] rework EAL argument parsing in DPDK Stephen Hemminger
2025-07-09 7:50 ` Bruce Richardson
2025-07-09 12:30 ` David Marchand
2025-07-09 12:54 ` Bruce Richardson
2025-07-17 10:41 ` David Marchand
2025-07-17 10:54 ` Bruce Richardson
2025-07-18 14:33 ` [PATCH v3 0/9] rework EAL argument parsing Bruce Richardson
2025-07-18 14:33 ` [PATCH v3 1/9] build: add define for the OS environment name Bruce Richardson
2025-07-18 14:33 ` [PATCH v3 2/9] argparse: export function to print help text for object Bruce Richardson
2025-07-18 14:33 ` [PATCH v3 3/9] argparse: allow user-override of help printing Bruce Richardson
2025-07-21 8:43 ` David Marchand
2025-07-21 9:00 ` Bruce Richardson
2025-07-18 14:33 ` [PATCH v3 4/9] eal: add long options for each short option Bruce Richardson
2025-07-18 14:33 ` [PATCH v3 5/9] eal: define the EAL parameters in argparse format Bruce Richardson
2025-07-21 8:41 ` David Marchand
2025-07-21 9:05 ` Bruce Richardson [this message]
2025-07-21 12:53 ` Bruce Richardson
2025-07-18 14:33 ` [PATCH v3 6/9] eal: gather EAL args before processing Bruce Richardson
2025-07-18 14:33 ` [PATCH v3 7/9] eal: ensure proper cleanup on EAL init failure Bruce Richardson
2025-07-18 14:33 ` [PATCH v3 8/9] eal: combine parameter validation checks Bruce Richardson
2025-07-18 14:33 ` [PATCH v3 9/9] eal: simplify handling of conflicting cmdline options Bruce Richardson
2025-07-18 14:41 ` [PATCH v3 0/9] rework EAL argument parsing Bruce Richardson
2025-07-21 15:08 ` [PATCH v4 " Bruce Richardson
2025-07-21 15:08 ` [PATCH v4 1/9] build: add define for the OS environment name Bruce Richardson
2025-07-21 15:08 ` [PATCH v4 2/9] argparse: export function to print help text for object Bruce Richardson
2025-07-21 15:08 ` [PATCH v4 3/9] argparse: allow user-override of help printing Bruce Richardson
2025-07-21 15:08 ` [PATCH v4 4/9] eal: add long options for each short option Bruce Richardson
2025-07-21 15:08 ` [PATCH v4 5/9] eal: define the EAL parameters in argparse format Bruce Richardson
2025-07-21 15:08 ` [PATCH v4 6/9] eal: gather EAL args before processing Bruce Richardson
2025-07-21 15:08 ` [PATCH v4 7/9] eal: ensure proper cleanup on EAL init failure Bruce Richardson
2025-07-21 15:08 ` [PATCH v4 8/9] eal: combine parameter validation checks Bruce Richardson
2025-07-21 15:08 ` [PATCH v4 9/9] eal: simplify handling of conflicting cmdline options Bruce Richardson
2025-07-21 15:16 ` [PATCH v5 0/9] rework EAL argument parsing Bruce Richardson
2025-07-21 15:16 ` [PATCH v5 1/9] build: add define for the OS environment name Bruce Richardson
2025-07-21 15:16 ` [PATCH v5 2/9] argparse: export function to print help text for object Bruce Richardson
2025-07-21 15:16 ` [PATCH v5 3/9] argparse: allow user-override of help printing Bruce Richardson
2025-07-21 15:16 ` [PATCH v5 4/9] eal: add long options for each short option Bruce Richardson
2025-07-21 15:16 ` [PATCH v5 5/9] eal: define the EAL parameters in argparse format Bruce Richardson
2025-07-21 15:16 ` [PATCH v5 6/9] eal: gather EAL args before processing Bruce Richardson
2025-07-21 15:16 ` [PATCH v5 7/9] eal: ensure proper cleanup on EAL init failure Bruce Richardson
2025-07-21 15:16 ` [PATCH v5 8/9] eal: combine parameter validation checks Bruce Richardson
2025-07-21 15:16 ` [PATCH v5 9/9] eal: simplify handling of conflicting cmdline options 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=aH4C06sBOa7q_tlg@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=roretzla@linux.microsoft.com \
--cc=thomas@monjalon.net \
/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).