From: David Marchand <david.marchand@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/2] use core lists not masks in documentation
Date: Thu, 3 Jul 2025 11:05:28 +0200 [thread overview]
Message-ID: <CAJFAV8zLPYDMo=wbBuYKF-oUA-kjzOMa7GmgoaX3cuMEjC7Duw@mail.gmail.com> (raw)
In-Reply-To: <20250624133409.550372-1-bruce.richardson@intel.com>
On Tue, Jun 24, 2025 at 3:34 PM Bruce Richardson
<bruce.richardson@intel.com> wrote:
>
> For real-world use with dozens if not hundreds of cores, use of core
> masks becomes unwieldy. Core lists are preferred so update the examples
> and DPDK docs to refer to core lists over core masks i.e.
>
> * use "-l" EAL option rather than "-c"
> * use "-S" service core list option rather than "-s"
>
> Bruce Richardson (2):
> doc/eal: add doc entry for service core list flag
> doc: use core lists rather than masks in guides
>
> doc/guides/bbdevs/acc100.rst | 2 +-
> doc/guides/bbdevs/fpga_5gnr_fec.rst | 4 +-
> doc/guides/bbdevs/fpga_lte_fec.rst | 2 +-
> doc/guides/bbdevs/vrb1.rst | 2 +-
> doc/guides/bbdevs/vrb2.rst | 2 +-
> doc/guides/cryptodevs/octeontx.rst | 2 +-
> doc/guides/eventdevs/dlb2.rst | 6 +--
> doc/guides/faq/faq.rst | 8 ++--
> doc/guides/freebsd_gsg/build_sample_apps.rst | 8 ++--
> doc/guides/howto/packet_capture_framework.rst | 2 +-
> doc/guides/linux_gsg/build_sample_apps.rst | 10 ++---
> doc/guides/linux_gsg/eal_args.include.rst | 5 +++
> doc/guides/mempool/cnxk.rst | 2 +-
> doc/guides/mempool/octeontx.rst | 2 +-
> doc/guides/nics/cnxk.rst | 2 +-
> doc/guides/nics/cpfl.rst | 2 +-
> doc/guides/nics/dpaa.rst | 2 +-
> doc/guides/nics/dpaa2.rst | 4 +-
> doc/guides/nics/fail_safe.rst | 8 ++--
> doc/guides/nics/ice.rst | 4 +-
> doc/guides/nics/softnic.rst | 4 +-
> 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/sample_app_ug/bbdev_app.rst | 6 +--
> doc/guides/sample_app_ug/ip_pipeline.rst | 2 +-
> doc/guides/sample_app_ug/ipsec_secgw.rst | 4 +-
> .../sample_app_ug/l2_forward_macsec.rst | 4 +-
> doc/guides/sample_app_ug/l3_forward.rst | 2 +-
> doc/guides/sample_app_ug/multi_process.rst | 8 ++--
> doc/guides/sample_app_ug/ntb.rst | 2 +-
> doc/guides/sample_app_ug/pipeline.rst | 2 +-
> doc/guides/sample_app_ug/qos_scheduler.rst | 2 +-
> doc/guides/sample_app_ug/test_pipeline.rst | 2 +-
> doc/guides/sample_app_ug/vdpa.rst | 2 +-
> doc/guides/tools/comp_perf.rst | 5 +--
> doc/guides/tools/cryptoperf.rst | 5 +--
> doc/guides/tools/graph.rst | 13 +++----
> doc/guides/tools/testbbdev.rst | 2 +-
> doc/guides/tools/testeventdev.rst | 39 +++++++++----------
> doc/guides/tools/testmldev.rst | 27 +++++++------
> 41 files changed, 110 insertions(+), 112 deletions(-)
Series applied, thanks Bruce.
--
David Marchand
prev parent reply other threads:[~2025-07-03 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 13:34 Bruce Richardson
2025-06-24 13:34 ` [PATCH 1/2] doc/eal: add doc entry for service core list flag Bruce Richardson
2025-06-26 13:36 ` Burakov, Anatoly
2025-06-30 11:18 ` Konstantin Ananyev
2025-06-24 13:34 ` [PATCH 2/2] doc: use core lists rather than masks in guides Bruce Richardson
2025-06-26 13:40 ` Burakov, Anatoly
2025-06-30 11:17 ` Konstantin Ananyev
2025-06-30 13:11 ` David Marchand
2025-06-30 13:31 ` Bruce Richardson
2025-07-03 9:05 ` 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='CAJFAV8zLPYDMo=wbBuYKF-oUA-kjzOMa7GmgoaX3cuMEjC7Duw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=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).