From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Bruce Richardson <bruce.richardson@intel.com>, dev@dpdk.org
Subject: Re: [PATCH v5 0/3] lcore options cleanup
Date: Mon, 23 Jun 2025 18:01:40 +0200 [thread overview]
Message-ID: <CAJFAV8wActb8OErY7T1qfk7mzmcYue+Am12Hbr=7nybNP0VYsg@mail.gmail.com> (raw)
In-Reply-To: <5697443.hdfAi7Kttb@thomas>
On Sun, Jun 8, 2025 at 11:12 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 27/05/2025 17:29, Bruce Richardson:
> > This patchset performs some basic cleanup of EAL lcore arguments before
> > any more serious work is done on them (as discussed in previous patchset
> > revisions).
> >
> > * mark the old coremask parameter (-c) and service core mask (-s) as
> > deprecated, so they can be dropped in future. Everything should now be
> > done using core lists where possible.
> > * consolidate the, previously separate but similar, "-l" and "--lcores"
> > flags into just short and long versions of the same thing. This does
> > not affect the "--lcores" flag at all, but expands the scope of what
> > was possible with "-l".
> > * Add documentation of examples of use of the -l/--lcores parameter
> >
> > V5: adjust the examples in patch 3, to only use quotes where necessary
> > and explain in a note why they are sometimes used in the examples.
> >
> > Bruce Richardson (3):
> > eal: deprecate old coremask-based EAL parameters
> > eal: merge corelist and core mapping options
> > doc: provide examples of using lcores EAL parameter
>
> This first step looks reasonnable,
> but we need more acks for the deprecation.
>
> Applied without the first patch deprecating the famous -c option,
> pending for a later stage in this release cycle.
Sorry, I wanted to review this series sooner.
It looks good to me, even though it is already applied.
The deprecation notice lgtm, I sent some comments on it.
--
David Marchand
prev parent reply other threads:[~2025-06-23 16:02 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 11:38 [RFC PATCH 0/3] allow easier use of high lcore-ids Bruce Richardson
2025-03-13 11:38 ` [RFC PATCH 1/3] eal: centralize core parameter parsing Bruce Richardson
2025-03-13 11:38 ` [RFC PATCH 2/3] eal: convert core masks and lists to core sets Bruce Richardson
2025-03-13 11:38 ` [RFC PATCH 3/3] eal: allow automatic mapping of high lcore ids Bruce Richardson
2025-03-24 17:30 ` [PATCH v2 0/3] allow easier use of high lcore-ids Bruce Richardson
2025-03-24 17:30 ` [PATCH v2 1/3] eal: centralize core parameter parsing Bruce Richardson
2025-04-07 6:58 ` David Marchand
2025-03-24 17:30 ` [PATCH v2 2/3] eal: convert core masks and lists to core sets Bruce Richardson
2025-04-07 6:59 ` David Marchand
2025-03-24 17:30 ` [PATCH v2 3/3] eal: allow automatic mapping of high lcore ids Bruce Richardson
2025-04-01 14:06 ` [PATCH v2 0/3] allow easier use of high lcore-ids Bruce Richardson
2025-04-07 7:04 ` David Marchand
2025-04-07 9:48 ` Bruce Richardson
2025-04-07 10:15 ` Morten Brørup
2025-04-07 10:40 ` Bruce Richardson
2025-04-07 11:32 ` Morten Brørup
2025-04-07 11:56 ` Bruce Richardson
2025-04-07 12:25 ` Morten Brørup
2025-04-07 12:41 ` Bruce Richardson
2025-04-07 13:18 ` Morten Brørup
2025-04-07 13:24 ` Bruce Richardson
2025-04-07 15:14 ` Stephen Hemminger
2025-04-07 15:38 ` Bruce Richardson
2025-05-02 15:11 ` [PATCH v3 0/4] rework and expand EAL lcore options Bruce Richardson
2025-05-02 15:11 ` [PATCH v3 1/4] eal: deprecate old coremask-based EAL parameters Bruce Richardson
2025-05-02 15:51 ` Stephen Hemminger
2025-05-02 16:00 ` Bruce Richardson
2025-05-03 6:09 ` Morten Brørup
2025-06-13 13:53 ` Bruce Richardson
2025-05-02 15:11 ` [PATCH v3 2/4] eal: merge corelist and core mapping options Bruce Richardson
2025-05-02 15:11 ` [PATCH v3 3/4] doc: provide examples of using lcores EAL parameter Bruce Richardson
2025-05-02 15:11 ` [PATCH v3 4/4] eal: add option for auto-mapping cpu ids to low lcore ids Bruce Richardson
2025-05-13 16:21 ` Bruce Richardson
2025-05-04 21:17 ` [PATCH v3 0/4] rework and expand EAL lcore options Patrick Robb
2025-05-13 16:17 ` [PATCH v4 0/3] lcore options cleanup Bruce Richardson
2025-05-13 16:17 ` [PATCH v4 1/3] eal: deprecate old coremask-based EAL parameters Bruce Richardson
2025-05-13 16:17 ` [PATCH v4 2/3] eal: merge corelist and core mapping options Bruce Richardson
2025-05-13 16:17 ` [PATCH v4 3/3] doc: provide examples of using lcores EAL parameter Bruce Richardson
2025-05-14 11:38 ` Morten Brørup
2025-05-14 12:14 ` Bruce Richardson
2025-05-27 15:31 ` Bruce Richardson
2025-05-15 15:11 ` [PATCH v4 0/3] lcore options cleanup Bruce Richardson
2025-05-27 15:29 ` [PATCH v5 " Bruce Richardson
2025-05-27 15:29 ` [PATCH v5 1/3] eal: deprecate old coremask-based EAL parameters Bruce Richardson
2025-05-27 15:34 ` Bruce Richardson
2025-06-23 16:01 ` David Marchand
2025-06-23 16:12 ` Bruce Richardson
2025-06-23 16:44 ` David Marchand
2025-05-27 15:29 ` [PATCH v5 2/3] eal: merge corelist and core mapping options Bruce Richardson
2025-05-27 15:29 ` [PATCH v5 3/3] doc: provide examples of using lcores EAL parameter Bruce Richardson
2025-06-08 21:12 ` [PATCH v5 0/3] lcore options cleanup Thomas Monjalon
2025-06-10 11:08 ` Varghese, Vipin
2025-06-13 13:51 ` Bruce Richardson
2025-06-23 16:01 ` David Marchand [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='CAJFAV8wActb8OErY7T1qfk7mzmcYue+Am12Hbr=7nybNP0VYsg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--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).