DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v5 1/3] eal: deprecate old coremask-based EAL parameters
Date: Mon, 23 Jun 2025 17:12:43 +0100	[thread overview]
Message-ID: <aFl8-3IuF9WU_YAe@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <CAJFAV8zpV=KUDha1tknK0cgv0cboG0htvJZ1kujtx=EJ7hXQHw@mail.gmail.com>

On Mon, Jun 23, 2025 at 06:01:00PM +0200, David Marchand wrote:
> On Tue, May 27, 2025 at 5:29 PM Bruce Richardson
> <bruce.richardson@intel.com> wrote:
> >
> > As the number of cores/cpus on platforms has increased over the years,
> > the use of coremasks rather than core-lists for identifying DPDK cores
> > has become more and more unwieldy. At this point, let's deprecate the
> > coremask-based EAL parameters for future removal, and point users to the
> > core-list based versions instead.
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > ---
> >  doc/guides/eventdevs/dlb2.rst                |  6 +++---
> >  doc/guides/faq/faq.rst                       |  8 +++-----
> >  doc/guides/linux_gsg/build_sample_apps.rst   |  7 +++----
> >  doc/guides/linux_gsg/eal_args.include.rst    |  8 ++------
> >  doc/guides/prog_guide/meson_ut.rst           |  2 +-
> >  doc/guides/prog_guide/multi_proc_support.rst |  2 +-
> >  doc/guides/prog_guide/service_cores.rst      |  8 ++++----
> >  doc/guides/rel_notes/deprecation.rst         | 10 ++++++++++
> >  doc/guides/sample_app_ug/ip_frag.rst         |  7 +------
> >  doc/guides/sample_app_ug/ip_reassembly.rst   |  7 +------
> >  doc/guides/sample_app_ug/multi_process.rst   | 14 +++++---------
> >  doc/guides/sample_app_ug/qos_scheduler.rst   |  2 +-
> >  doc/guides/sample_app_ug/test_pipeline.rst   |  2 +-
> >  doc/guides/tools/testbbdev.rst               |  2 +-
> >  lib/eal/common/eal_common_options.c          |  6 ++++++
> >  15 files changed, 43 insertions(+), 48 deletions(-)
> 
> This patch will need some rebase.
> 
> I see you fixed a few docs, but there are quite some misses in
> copy/pasted blocks:
> 
I'll take a look and respin this.

I'm think of separating it into two patches: first patch with the doc
updates to remove use of -c flag. This should happen independent of the
deprecation, I think, and second patch just the deprecation notice. Does
that sound reasonable?

/Bruce

  reply	other threads:[~2025-06-23 16:13 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 [this message]
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

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=aFl8-3IuF9WU_YAe@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.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).