DPDK patches and discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, david.marchand@redhat.com,
	mb@smartsharesystems.com,  stephen@networkplumber.org
Subject: Re: [PATCH v3 0/4] rework and expand EAL lcore options
Date: Sun, 4 May 2025 17:17:49 -0400	[thread overview]
Message-ID: <CAJvnSUCCtrzXMKALi6UpnpMD__M1Y+T3z8de+3TFNPJqE+LS-A@mail.gmail.com> (raw)
In-Reply-To: <20250502151134.536799-1-bruce.richardson@intel.com>

[-- Attachment #1: Type: text/plain, Size: 3187 bytes --]

Please disregard the Community Lab DTS failure just reported on this
patchseries. I need to reconfigure the testbed and rerun the test.

On Fri, May 2, 2025 at 11:11 AM Bruce Richardson <bruce.richardson@intel.com>
wrote:

> Following discussion earlier on this thread on the previous RFCs and
> patches submitted [1], this series is a slightly different take on
> solving the same fundamental problem - making it easy to use CPU cores
> with ids >= RTE_MAX_LCORE, without having massive amounts of code
> complexity internally. As previously discussed[2] this patchset
> implements proposal "2a" and does the following:
>
> * marks 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.
> * consolidates 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".
> * a new flag, with long/short versions, is added as "-L" to allow the
>   user to just specify a range or set of physical CPU core ids to be
>   used by the app, and have them automatically mapped internally to a
>   set of lcore ids starting at 0. This provides the "easy solution" to
>   the original problem stated above.
>
> For completeness, since it's in the same area, the previously separate
> documentation patch, adding examples for the "--lcores" parameter, is
> rolled into this series as patch 3.
>
> [1] https://patches.dpdk.org/project/dpdk/list/?series=34911&state=*
> [2]
> https://inbox.dpdk.org/dev/Z_PIBLQIT3eu6Ab3@bricha3-mobl1.ger.corp.intel.com/#t
>
> Bruce Richardson (4):
>   eal: deprecate old coremask-based EAL parameters
>   eal: merge corelist and core mapping options
>   doc: provide examples of using lcores EAL parameter
>   eal: add option for auto-mapping cpu ids to low lcore ids
>
>  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     |  61 ++++--
>  .../prog_guide/env_abstraction_layer.rst      |   3 +-
>  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           | 202 +++++++-----------
>  lib/eal/common/eal_options.h                  |   6 +-
>  lib/eal/windows/include/sched.h               |   1 +
>  18 files changed, 168 insertions(+), 182 deletions(-)
>
> --
> 2.45.2
>
>

[-- Attachment #2: Type: text/html, Size: 4089 bytes --]

      parent reply	other threads:[~2025-05-04 21:22 UTC|newest]

Thread overview: 32+ 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-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-04 21:17   ` Patrick Robb [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=CAJvnSUCCtrzXMKALi6UpnpMD__M1Y+T3z8de+3TFNPJqE+LS-A@mail.gmail.com \
    --to=probb@iol.unh.edu \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.com \
    --cc=stephen@networkplumber.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).